Flow map
SampleThe work as it is really done, from request to invoice. Here, everything waits for a single signature.
No hundred-page report. Short working documents, which leadership can arbitrate and a team can use from Monday, and systems that run in production.
Film · coming soonA steering system: mail sorted, the day prepared, replies proposed, nothing goes out without approval. Designed, built and operated by Nominal, it shows that the architecture advised is delivered and holds in production.
See the CockpitEach area of expertise has its own tools. Here are seven, as they appear, with sample data.
The work as it is really done, from request to invoice. Here, everything waits for a single signature.
| Decision | Leadership | Manager | Team | HR |
|---|---|---|---|---|
| Plan the week | I | D | F | |
| Arbitrate an emergency | D | D | F | |
| Recruit | I | D | F | |
| Approve an expense | D | F |
One row in amber: two people decide the same thing, so in effect nobody does.
Each decision has its forum, and each forum has its reason for being. The rest is dealt with outside meetings.
| Risk | Prob. | Impact | Owner |
|---|---|---|---|
| Key users unavailable during the testing phase | Business lead | ||
| Data migration taking longer than planned | IS lead | ||
| Supplier late on the interface | Programme management | ||
| A team's resistance to the new process | Team lead |
Each risk has an owner and a mitigation. The one that crosses the threshold turns amber and goes up to the committee.
What exists, what is redundant, and where data gets lost. The drift is marked in amber.
What is done now, what comes next, and what must hold in a year.
Few figures, looked at every week, early enough to decide. The one that drifts is seen immediately.
Typical examples, with no real client or figure.
Engagements are published here once completed, and only with the agreement of the clients concerned. Confidentiality comes before the showcase.