Innovation gives us the approaches. Constant management gives us clarity, maturity and experience. A project needs both: without structure it loses its way, without new approaches it stalls.
The constant: structure
From one project to the next the structure stays the same, because experience has shown us what keeps a project on track: what we actually want, in what order we work, how we know we are done, what we decided and why, and what we learned. These are the classic principles of project management, kept whole. The six-step process is on our Project Management page.
The variable: the approach
For each challenge we bring a fitting, often unusual approach. The concepts are our own; we do not adopt a ready-made method. Sometimes new forms emerge, yet each one is rooted in a known principle. We have a solid base and keep it moving: what we learn in one project benefits all the others.
How the two fit together
| Structure (constant) | Approach (innovation) |
|---|---|
| What we actually want (discovery) | Inventory before the plan: first what already exists and what the person really needs |
| What we set out to do versus what we deliver (traceability) | Mesh management: a mesh that shows early when we drift |
| How we know we are done (completion criterion) | "Done when": every step knows its end from the start |
| In what order we work (critical path) | Steps by dependency, not by calendar |
| What we decided and why (decision log) | The target in written versions, in the client's own words |
| Who chooses (vision workshop) | The client chooses among several readings, instead of approving a single one |
| What actually exists ("as built" documentation) | The picture: manuals and processes that renew themselves from what was built; what they show flows back into the concept and enriches it |
| What we learned (retrospective) | The lesson travels back: what we learn in one project applies in all |
| How we deliver (iterative delivery) | Build first, refine after |
What sets us apart
The principles are the same everywhere. The difference is the loop: for our larger projects we keep a picture of what actually exists, drawn from what was built, in manuals and processes that renew themselves automatically and are checked quickly. The picture flows back into the concept: what we see there corrects and enriches it. So the structure stays clear, and our approaches improve from what really happened.
Our niche
Our niche is projects of high complexity and close attention to detail. We hold them together with mesh management, the mesh that ties the parts to one another. Within them we work where people and systems meet. First, dashboards: the picture is read on a dashboard, and designing them is our niche, clear and dense panels for the people who use them every day. Second, the interface between AI agents and people: we study how to manage agents so that they support human operators rather than replace them. This is where, we believe, the usefulness of AI is decided.
With the client
Here the structure is a collaboration plan we follow; the approach is to keep it flexible: steps move when reality changes, not when the calendar does. Our rule: every case has a chronology with a red thread, meaning motivation and logic, not just dates. Communication lives in the product, in a single thread per order in which everyone involved speaks. And we want to capture the idea of the moment where it arises.
Volunteering
For a public-speaking club run by volunteers we build, on our own initiative, the tools it uses to run its meetings. They are in regular use. There, initiative, rotating roles and partnership set the tone, at a lean pace; what we learn flows back into the firm's projects.
An idea for later: the same logic, put at the service of other small communities.
Red threadBehind every project stands a person. The structure ensures they do not have to keep everything in their head; the approach ensures that what they receive fits them.