Embedded governance · Project balancer
An advisory practice that smooths the seams between business, operations, and engineering — so that projects and organisations can move forward safely. Strongest at the start of new projects, at the first signs of trouble, and for early-stage startups.
Close enough to the work to understand it; far enough back to keep perspective. Decisions, agreements, and implementation — all kept in shape.
Problems
Most of the time, what threatens a project's safety isn't the technology — it's the resolution at which people see each other.
Philosophy
What keeps a project moving is rarely a stronger directive or a fancier method. It is the willingness to question assumptions, sharpen judgement, and put everyone on solid ground before the next step.
Respect for what business teams actually feel. Respect for what engineering has to actually build. Respect for what decision-makers actually need to see. The work is to keep all three in proportion, without taking a side.
Rather than blaming failure, build structures in which failure is harder. Rather than selling hours of labour, raise the quality of judgement and agreement. That is the stance behind every engagement.
Primary entry points
Most engagements begin through one of two routes. The entry point depends on where the project stands — before it moves, or once early signals suggest it is already drifting.
New project
Before a project starts running, set the goals, requirements, stakeholders, decision structure, risks, and exit criteria. Putting the structure in place early reduces rework downstream and narrows the gap between business strategy, operations, and technology delivery.
Course correction
When rework, misunderstandings, friction between departments, or stalled approvals start to surface, we step in before the situation escalates. We make the misalignments visible and help re-establish priorities and shared agreements — adjusting the structure rather than blaming the people in it.
Common contexts
These are not additional entry points. They are the consulting contexts in which the two primary entries are most often applied.
Alignment
Non-IT stakeholders and actual users are included in requirements, decision-making, and adoption. Bridging the gap between what business needs and what development builds.
Decision support
Risks, trade-offs, and options are structured into clear materials for approvers and project owners — so that the people authorising work understand what they are authorising.
Startup
For founders, product leaders, and development leaders navigating business goals, product decisions, technical structure, and early organisation design — all at once. This is not a third primary entry point; it is a consulting context that usually begins through Foundation Design or Project Rebalancing.
Phases
New projects
While requirements and assumptions are still fluid, work on foundations and guardrails — so that less has to be undone later.
Early signs of fire
When rework and mismatches are starting to compound, organise the points and rebuild agreement — before the situation escalates further.
Next steps
Engagement scope, applicable phases, what is and isn't taken on, how the work moves.
Pricing at a glance
Priced by scope and depth of involvement, not by hours alone. Final figures are quoted individually based on size, duration, and frequency.
Indicative ranges
Trust
More about the people, and more about the work, on their own pages.
The company providing the service and the stance behind it.
About re:flerdAnonymised examples of past engagements and the changes that followed.
See casesGet in touch
We can start from organising the situation. No prep deck, no internal sign-off needed beforehand. Whatever you can share is enough to begin.
Open the contact form