The Polymath practice: generalists with deep specialties, one method across every engagement, and the discipline to measure before we recommend.
The problems worth hiring a firm for do not respect the boundaries between strategy, operations, finance and data. A portfolio that will not prioritize is usually a finance problem and a governance problem at once. A process that keeps failing is usually a data problem and a leadership problem. Specialists see their slice. We staff people who have run operations, closed books, built data systems and structured decisions, and who can hold the whole problem in view while going deep where it matters.
A method the client can read is a method the client can hold us to. Ours is documented, applied the same way on a finance transformation as on a program rescue, and being written up as a published framework, with the first edition in development. It borrows from four traditions that turn out to agree on the essentials and disagree mostly on vocabulary.
The explicit discipline of scope, schedule, cost, quality, risk, resources, communication and stakeholders, from the Project Management Institute's body of knowledge. It gives the work a common vocabulary and an auditable structure.
Structured planning under uncertainty, courses of action compared before one is chosen, rehearsal before execution, clear intent that lets the team exercise judgment, and the after-action review. Civilian organizations rarely rehearse a plan. It is the highest-leverage habit we bring.
Define and measure before improving; control after. DMAIC for a process that is failing, DMADV for one that does not exist yet, and the statistical honesty to know the difference between a change and an improvement.
Hypothesis-driven analysis, issue trees that are mutually exclusive and collectively exhaustive, and conclusions communicated top down. The tools the major firms use to make a complicated problem decidable.
Every engagement runs on four phases: Plan, Prepare, Execute, Assess. They are continuous and simultaneous, not a sequence. Planning continues while the work is under way. Preparation starts before the plan is finished. Assessment begins on the first day, not at the end.
Mission analysis first: what is actually being asked, what constrains it, what has to be true for it to work. Then courses of action developed, tested and compared before one is chosen, and the plan written with explicit scope, schedule, cost, risk and decision points.
People, information and authorities positioned before the start. Reporting cadence, escalation path and decision rights agreed. The plan walked through with the team, with the contingencies named and the points where it may need to change identified in advance.
Clear intent, then disciplined initiative inside it. The team acts, observes the result and adjusts on a fixed cycle. Decisions are logged as they are made, so the record exists before anyone needs it.
Measurement runs concurrently, not afterward. Structured after-action review on the Army's four questions, controlled improvement of the recurring operation, and lessons captured where the next planning cycle will find them.
We do not recommend what we have not measured. A diagnostic establishes the baseline, inventories the portfolio, maps the processes and reads the numbers as they are rather than as reported. It is a small engagement on purpose: it earns the right to propose the larger one, and sometimes it shows that the larger one is not needed.
Every deployment sits on a library of 162 master templates across twelve operational categories: Excel workbooks, Power BI files and SharePoint structures that share one architectural standard. It is why a dashboard ships in weeks rather than months, and why each later layer builds on the last instead of replacing it.
A documented, operating system rather than a deck: the templates configured, the workflows running, the people who own them trained, and a measurement cadence that keeps reporting after we leave. If it only works while we are in the building, we have not finished.
Bring the problem as it is. The first conversation is about whether it can be fixed, not about selling the fix.
Start a conversation