30/90/365: How to Size Operational Changes Honestly

A firm invests $30,000 in an operational improvement. The proposal promises $180,000 in annual savings. Twelve months later, nobody can say whether the savings materialized — because nobody defined what "savings" would look like at 30 days, 90 days, or any point before the annual mark.

The 30/90/365 Sizing model is Cendia’s framework for scoping every operational recommendation against three time horizons. What changes visibly in 30 days. What’s measurable at 90 days. What the financial return looks like at 365 days. If a recommendation can’t articulate a 30-day milestone, it’s too vague to implement. If it can’t project a 365-day return, it’s too speculative to invest in. The model forces honest scoping by requiring concrete answers at each horizon.

Every Cendia recommendation passes through this sizing. It’s also the filter we recommend for evaluating anyone else’s — consultants, vendors, internal proposals.

Why annual ROI projections fail

Annual ROI projections are the standard currency of operational proposals. They fail for a specific, structural reason: they compress an entire year of assumptions into a single number with no intermediate checkpoints.

A $180,000 annual savings projection might assume: the new process is adopted within 30 days (it takes 90), the error rate drops by 60% (it drops by 35%), the team reallocates recovered hours to billable work (they don’t — the hours get absorbed by other operational tasks). Each assumption is reasonable in isolation. Together, they produce a projection that’s 40-60% higher than the actual outcome — and nobody discovers this until month 12, if they measure at all.

Cendia’s observation across 20+ engagements: fewer than 25% of services firms in the 30-100 person range measure the actual ROI of operational changes they’ve implemented. The projection is the pitch. The measurement never happens. The result: firms repeat investments in change types that don’t produce returns, because they never verified whether previous changes worked.

The three horizons and what each measures

30/90/365 Sizing defines a specific type of milestone at each horizon. The three horizons measure different things.

Each horizon serves a different function in the decision process.

30-day milestones prevent vague implementations. An operational change with no visible result at 30 days is either too large (needs to be broken into smaller phases), too abstract (needs a concrete first step), or stalled (the team hasn’t actually changed anything). The 30-day check catches all three failure modes early enough to intervene.

90-day milestones separate real change from activity. A new process can be “in place” at 30 days without producing any measurable improvement. The process exists, the team uses it, but the metrics haven’t moved. At 90 days, enough data has accumulated to judge whether the change is working. If the metric hasn’t moved by day 90, the change needs revision — not more time.

365-day milestones anchor the financial case. Annual return is where the investment math lives. The Three-to-One Rule applies: a change must produce 3x its implementation cost within 12 months to justify the disruption it created. Below 3x, the organizational cost of implementing the change — retraining, transition friction, temporary productivity loss — consumes most of the value.

How to build a 30/90/365 plan for any operational change

Five steps, completable in 2-3 hours for a single initiative.

Step 1: Define the change in one sentence. “We’re implementing a structured handoff document for the sales-to-operations transition” is specific enough. “We’re improving our client onboarding process” is too broad — it could mean 15 different things, and the team will disagree about which one.

Step 2: Write the 30-day milestone. Ask: what will be visibly different in 30 days if this change succeeds? The answer must be binary — observable as done or not done. “The handoff document template exists, the team has been trained, and it’s been used on 10+ new engagements” passes. “The team is more aligned on handoffs” does not.

Step 3: Write the 90-day milestone. Ask: what metric will have moved by day 90? Name the specific metric, the current baseline, and the target. “First-30-day rework hours per engagement drop from 4.0 to 2.0” passes. “Rework is reduced” does not. If you can’t name the metric or the baseline, you need to measure before you implement — the change might already be working, or the problem might be smaller than assumed.

Step 4: Write the 365-day projection. Calculate the annualized financial return based on the 90-day metric target. If first-30-day rework drops from 4 hours to 2 hours across 72 engagements per year at a loaded rate of $165/hour, the annual savings is $23,760. Compare this to the implementation cost. If the return exceeds 3x the cost, the change passes the Three-to-One Rule. If it doesn’t, the change may still be worth doing — but the justification needs to come from something other than financial return (risk reduction, client satisfaction, team retention).

Step 5: Define the measurement method. How will each milestone be tracked? Who owns the measurement? When will the check happen? Without assigned ownership, milestones become aspirational — technically defined but never verified. Assign a single person to each horizon check: “On day 30, the operations director confirms the template is in use. On day 90, the operations director pulls rework data and reports to leadership.”

A complete 30/90/365 example

A 62-person digital agency engaged Cendia because their CEO was spending 8-12 hours per week on operational decisions that should be handled by the operations director. The Surface vs. Structure Lens identified the structural cause: 25 recurring operational decisions had no documented criteria.

The intervention: document decision rules for the top 10 decisions by frequency.

Actual results: at 30 days, all 10 decision documents were complete. At 90 days, CEO operational hours had dropped from 10 hours/week (baseline) to 4 hours/week — a 60% reduction. At 365 days, the annualized recovery was 312 hours at an effective rate of $300/hour: $93,600 against an $8,500 implementation cost. Return: 11x.

The 30-day milestone caught one issue early: decision rule #4 (vendor approval thresholds) was too vague and the operations director was still escalating vendor decisions to the CEO. The rule was revised at day 35. Without the 30-day check, this gap would have persisted for months — reducing the 90-day result.

How to use the model to evaluate external recommendations

Every consulting proposal, vendor pitch, and internal improvement request can be filtered through 30/90/365 Sizing. Ask three questions:

“What will be visibly different at 30 days?” If the vendor or consultant can’t answer this specifically, the proposal lacks a concrete implementation plan. “We’ll begin the discovery phase” is not a 30-day milestone. “Your team will have a documented handoff spec for 3 workflows” is.

“What metric moves at 90 days, and by how much?” If the answer is vague (“efficiency improves,” “the team operates more smoothly”), the proposal can’t be measured. Unmeasurable proposals can’t be verified. Unverifiable proposals are how firms spend $40,000 on consulting engagements that produce slide decks and nothing else.

“What’s the 365-day financial return, and does it clear 3x?” If the return is below 3x the implementation cost, the disruption of implementing the change likely outweighs the value. This doesn’t mean the recommendation is wrong — it means the financial case is weak and the justification needs to stand on other grounds.

Cendia’s finding: roughly 40% of operational recommendations that sound compelling in a presentation fail the 30/90/365 test — usually at the 30-day milestone, where the recommendation turns out to be too vague to produce a specific first action.

The proposal promises $180,000 in annual savings. The 30/90/365 question: what's visibly different in 30 days? If the answer is blank, the savings are speculative — and speculation is how firms spend $30,000 to buy a slide deck.

What this isn’t

Scope notes:

• This isn’t a guarantee of ROI. The model forces honest projection, not accurate prediction. External factors can change outcomes. The value is that assumptions become explicit and checkpoints happen early — failures are caught at day 30, not discovered at month 12.
• This isn’t applicable to every type of change. Brand repositioning, culture shifts, and long-term strategic pivots don’t produce 30-day visible milestones. The model is designed for operational improvements with measurable cost or time components.
• This isn’t a substitute for doing the work. A beautifully written 30/90/365 plan that nobody executes produces the same result as no plan. The model’s power comes from the measurement cadence — the 30-day and 90-day checks that force accountability and course correction.

FAQ

What if the 30-day milestone is met but the 90-day metric doesn’t move?

This is the most common failure pattern: the change was implemented but didn’t produce the expected impact. At day 90, you have three options — revise the approach (the implementation was correct but the mechanism was wrong), expand the scope (the change was too narrow to move the metric), or stop (the hypothesis was incorrect and further investment won’t produce returns). All three options are better than continuing to invest without data.

How do we set realistic 90-day targets?

Use the baseline measurement as the anchor. If current rework is 4 hours per engagement, a 50% reduction target (to 2 hours) is aggressive but achievable for a structural fix. A 20-30% target is conservative and appropriate for incremental process changes. Avoid targets that require behavioral change from the entire team — those take 6-12 months, not 90 days.

Can we use 30/90/365 for changes that don’t have a direct financial return?

Yes. Replace the 365-day financial milestone with the outcome that matters: client satisfaction score improvement, employee retention rate, compliance audit pass rate. The Three-to-One Rule may not apply directly, but the 30-day and 90-day milestones still provide the same accountability structure.

How does this interact with the other Cendia frameworks?

The 30/90/365 Sizing model is the output layer. The diagnostic frameworks (Handoff Cost Model, Cost-Per-Workflow, The Surface vs. Structure Lens) identify what to fix. The decision frameworks (Eliminate-Before-Automate, Build vs. Buy vs. Eliminate) determine how to fix it. 30/90/365 Sizing defines when the fix should produce results and how to measure whether it did.

This article is part of Cendia’s Operational Frameworks series. Companion pieces cover the Handoff Cost Model, Eliminate-Before-Automate, and Cost-Per-Workflow — the diagnostic and decision frameworks that 30/90/365 Sizing measures against.