Perspectives
We came. We saw.
We solved.
The space is evolving. The approach is proven.
Articles and signals on how people, process and technology are changing, and how enterprises can turn that change into value.
The method underneath
Four disciplines. One operating model.
Every paper here resolves onto one of the four disciplines we deliver. That is the point of it: the foundation that settles a reporting problem is the foundation that settles an M&A one, so the second problem costs less than the first and the third less again. The library grows as the work does.
Foundational Architecture
Process Redesign
11Owning the Conversion from Strategy to Work draws on all four — it is why they are one engagement rather than four separate ones.
Foundational Architecture
Where a number, a role or a rule is defined, who may change it, and what everything downstream inherits. Settle it once and the next problem starts from something that already exists.
From Data Lake to Decision Layer
Why finance keeps rebuilding the number in Excel — and what it takes to stop
Excel is not the failure. In most enterprises it is the only place where a named person is accountable for a number.
Where we start
We start with a short pass across your Record-to-Report cycle: for the ten to fifteen figures your executives actually decide on, we establish who produces each one and who may change its definition.
Building a CEO/CFO-Ready Reporting Infrastructure
Four functions, four correct answers, one question, nobody owning the seam
An executive reporting layer is a governance artifact, not a BI artifact. Its job is to make one number defensible in a room holding four correct ones.
Where we start
We start with a working session rather than a build: the ten questions your board asks across segments, and which hierarchy, calendar and unit governs each answer.
M&A Value Realization
Deal models are built in categories; operations only ever pays in instances
A deal model is written in categories because categories are all diligence can see. Operations runs in instances, and nobody owns the conversion between them.
Where we start
We start before signing where your timing allows, converting each synergy line into the operating objects it depends on: the position architecture, the pay calendar, the filing entity.
The 98% Problem
How a workforce forecast gets to 98% accuracy — by fixing the records, not the model
Workforce forecast error is not spread across the population. It concentrates in the few records where an employment event and its cost have parted company.
Where we start
We start with two closes and a list of names: we decompose your recent workforce variance to individual records, which settles where the error actually sits.
Global HRIS Modernization Done Right
Local variation arrives as a configuration request. It is never a configuration question.
Global versus local is not a configuration debate. It is a decision-rights debate in a configuration costume, settled by whoever happens to be in the room.
Where we start
We start before design freeze, with your five highest-volume Hire-to-Retire processes taken role by role, and every role that touches them written as decision rights rather than as job titles.
IPO Readiness Starts with Compensation Governance
The grants you made three years ago become disclosure the year you list
Compensation governance has a longer lead time than the listing. A private decision is complete when it is made; a public one must survive people who were never in the room.
Where we start
We start with an inventory of what cannot be evidenced: we pull every award outstanding in your plan and source approver, authority, effective date and vesting from documents alone.
From Headcount to Strategy
You can say how many people you have. Can you say which capability you cannot buy?
Headcount is counted in roles because roles are what the system stores. Strategy consumes capabilities, and no system stores those.
Where we start
We start against your roadmap rather than your organization chart: we take the commitments carrying capital, match them one at a time to the role data you already hold, and write down the exceptions.
Process Redesign
What the work actually consists of, step by step, before anyone configures a system around it. The return on a platform is decided here, not at go-live.
Where ERP Returns Are Actually Decided
The return is traded away in design meetings, long before anyone measures it
ERP returns are decided in the design phase and merely observed at go-live. By stabilization you are negotiating with choices made a year earlier.
Where we start
We start in the narrow window your programme leaves open — after your business case is approved, before your design freezes — because that is where the return is still available to be taken.
Predictive Analytics for the Enterprise
Why the numbers you argue with are the ones nobody agreed to
A forecast of internal performance predicts how named people will behave. If they did not set the assumption, you have measured them rather than planned with them.
Where we start
We start inside one live reforecast cycle of yours, listing every assumption that moves the number as it is actually produced and setting each one against the person who owns the decision underneath it.
Bottom-Up Transformation
The workaround is not defiance. It is the specification nobody wrote down
Low adoption is a design verdict, not a change failure. The workaround your people built is usually better than the process you asked them to follow.
Where we start
We start with your process as performed rather than as documented: we sit with the people running it and record what is actually done, in what order and in which tool, including the spreadsheets.
Removing Work, Not Moving It
Why a cut that moves work instead of removing it still books as a saving
Cost lives in a budget. Work lives in a process. Cut the first without redesigning the second and you have moved the work, not removed it.
Where we start
We start with your target itself, before it becomes a plan: we trace every contract and role inside the number to the process steps it actually carries.
Hire to Retire Runs on One Event
The hire happened once. Whether it is entered once is an architecture decision, not an HR one.
An employment event happens once. Every system downstream should inherit it, and wherever it is re-entered instead, the re-entry has quietly become the process.
Where we start
We start with one hire and one termination of yours, and we follow each of them by hand to every place the same fact is entered again, sitting with the person who enters it.
AI Enablement
The judgment that decides your exceptions, written down in the words of the people who hold it. That is what an agent needs and what no model supplies.
AI in the Enterprise
Your processes have a documented path and an actual path. Only one is written down
The binding constraint is not model capability. It is that your enterprise cannot supply the judgment that decides its exceptions, because that judgment was never written down.
Where we start
We start where your deployment stalls, not at a use-case workshop: one process — the exception path in Order-to-Cash — and four answers for every decision an agent would take.
One Demand Signal, Four Currencies
Your four forecasts are not four opinions about one number. They are four different quantities
You do not have four forecasts because four teams disagree. You have four because each is a different quantity, and no one in the company owns the conversion between them.
Where we start
We start inside the planning cycle you are already running, converting the four forecasts into one another — units to shipments to revenue to margin to consumption — and writing down every factor the conversion needs.
Change Management
The internal time a change actually costs, priced before the work starts rather than discovered eighteen months in.
Pricing the Internal Time a Transformation Costs
The business case prices the platform and the integrator. It never prices your own people.
Every transformation runs on internal time that appears in no budget. Time with no price is not allocated. It is taken, from whoever will not refuse.
Where we start
We start with arithmetic rather than a diagnosis of culture: we convert the work already in flight into named internal weeks and set them against what those same people already carry.
Letting the Person Who Knows the Fact Record It
Automation here does not remove work. It moves authorship to the only person who cannot get it wrong
Your hiring process puts two transcriptions between the person who knows a fact and the system that stores it.
Where we start
We start with one Hire to Retire process you have already put on the platform and ask a narrower question than the business case did: for every field in it, who knows this fact first, and how many people handle it between them and the record.
Designing the Roles Before Anyone Knows Who Fills Them
A merger asks the same people to draw the organization and to compete for a place in it
A resourcing synergy is not a headcount number. It is a set of jobs that has to be designed before anybody can be selected into or out of them.
Where we start
We start with the resourcing line in your own case and ask what it is a claim about — not how many people leave, but which positions the combined company intends to have.
Shipping the Org Design With the System
The process changed at go-live. The jobs, spans and objectives describing the old one did not
Nobody defies a new system. People follow their objectives, and their objectives were written for the process the system replaced.
Where we start
We start with the objectives your people are being measured on this year, read beside the process the system now runs, and we mark every line committing somebody to a step the release removed.
Across all four
Owning the Conversion from Strategy to Work
Converting strategy into each function’s work is real labour, and it is on nobody’s job description
Strategy is set above every function and executed below every function. The conversion between them is real work that sits in no budget and no mandate.
Where we start
We start with a conversion audit: we ask each of your functions for its own written interpretation of the same enterprise commitments, in its own units, on one page, by a date.
The other thirteen papers each sit inside one discipline. This one does not, and that is the argument: the conversion from strategy into each function’s work touches all four, which is why it is one engagement rather than four separate ones.
Start here
Start with the one you recognise.
Pick the paper closest to something you are living with now. It will tell you what is actually causing it, what we changed when we owned it, and what that returned. If it lands, the next step is one process and a working session — and you will already know how we think before we meet.
- 01 Read a paper
- 02 Bring one process to a working session
- 03 Build one workflow with one team
- 04 Run it as an engagement