
What Needs to Be Clear Before Development Starts?
Early decisions shape design and delivery, from defining the problem to agreeing observable acceptance scenarios.
Read articleArticles by Ali Seyednejad
Practical perspectives on the decisions that shape software: discovery, architecture, data, integration and responsibility after handover.


Early decisions shape design and delivery, from defining the problem to agreeing observable acceptance scenarios.
Read article
A sound technical and commercial choice starts with the real difference between your workflow and an existing product.
Read article
Before writing the connection, define data ownership, the meaning of states and what each system does when something fails.
Read article
Choose a path for an existing system by understanding business risk, data and dependencies.
Read article
Language affects user journeys, forms, dates and layout direction; translated words are only part of the design.
Read article
A successful payment needs a clear meaning in order status, financial records and discrepancy handling.
Read article