Short notes on what each part of the tool is for and how to use it — the same notes the app shows beside your work.
If you are about to start a new software initiative, factor10 Solution Designer can help you think through all the necessary aspects of designing a…
Decentralised decision making requires that everyone understands why. The Strategy briefing captures exactly that (in as short and clear a form as…
A list of questions on concerns that cut across most software initiatives and are worth thinking through. What is utterly obvious, and therefore easy for…
Domain knowledge is usually scattered across several people at once: business folks, developers, operations, support. No single person holds the whole…
A software initiative is justified by the effect it has, not by what it contains. And there is always someone who gets that effect. It could be a…
Practices (for example review routines, test strategies, demo rhythm) change and get tuned over time. Values and principles do not. Or if they do, it is a…
Understanding the intention at several levels is of course extremely important, but it is at least as important to understand the context our initiative…
A software system beyond a certain size no longer fits in a single model. Try anyway and the language erodes: the same word means different things in…
Sometimes it is useful to describe certain key functionality within a Bounded Context, other times you just know that some things have to be included. The…
The user interface is the place where every other decision meets reality. A solution can have a well-suited architecture, but if the user cannot get their…
External endpoints and events are the public commitment a Bounded Context makes to the outside world. Everything else can change freely: the data model…
Conway's Law says the system will mirror the communication structures of the organisation that builds it. That means the team structure is part of the…
The ability to deliver often and reliably rests on automation. What a human runs gets run rarely, irregularly and with varying care; what a pipeline runs…
Operations is not a separate phase that begins once development is done. It is part of the solution's design. Where the components run, who owns them and…
Many decisions in a software initiative rest on uncertainty: about performance, about whether a third-party API behaves as documented, about whether an…
This is not about budgeting. It is a deliberate attempt, at an early stage, to put an order of magnitude on the initiative's effect over the first three…
An initiative is usually surrounded by background material: requirement specs, existing architecture sketches, market research, regulatory documents. If…
The Introduction is the opening section of your PDF export, and nothing else. It does not add a working canvas. It is only the prose that greets the…
The tool is not the final delivery itself. What actually moves on (to a customer, a leadership group, a contract or a git repo) are the artefacts that get…