The best software requirements are often hiding in exceptions.
The happy path tells you what a process wants to be. The exception tells you what it actually is.
Workshop note / coming soonNOTES THINGS WE LEARN WHILE MAKING
Fresh angles.
Useful ideas.
Short observations from building software around real operations. No invented thought leadership and no daily posting machine.
SCROLL TO EXPLOREContinue ↓
When a rewrite is the wrong answer.
Repairing a working system can create more value than replacing its technology.
Workshop note / coming soonDesign for the 300th click, not the first screenshot.
Operational interfaces have a different job from launch pages.
Workshop note / coming soonPeople should not become APIs between software.
If a person copies the same data between two systems all day, the architecture is asking for help.
Workshop note / coming soon03 TOPICS WE KEEP RETURNING TO
OPERATIONAL UIWORKFLOW DESIGN.NETAUTOMATIONDATA STATESUPPORTPERFORMANCEHANDOFFS
04 FIELD OBSERVATIONS
“The exception is often more useful than the happy path.”
“A fast repetitive screen should be designed differently from a launch page.”
“People copying data between systems is an architecture smell.”
“A rewrite is not automatically a modernization.”
HOW WE WRITEOne useful observation
One useful observation
at a time.
Start from something we actually saw while building.
Prefer concrete workflow language over trend language.
Explain the tradeoff, not just the opinion.
Leave room for the reader’s context to be different.
HAVE A REAL PROBLEM?The conversation is usually
Start a conversation ↗