Not every Key Result progresses linearly. A guide to selecting and modifying plan shapes that match real-world execution patterns.
The Default Is Almost Always Wrong
When you create a new Key Result in most OKR tools — Profit.co included — the system generates a default plan: linear distribution. The target is divided equally across all check-in periods. If your KR goes from 0% to 100% over 13 weeks, the default gives you approximately 7.7% per week, every week, for the entire quarter.
This is a reasonable starting point and a terrible finishing point. Almost no real-world outcome progresses at a constant rate. Sales pipelines accelerate as deals mature. Product adoption follows an S-curve as early users drive word-of-mouth. Engineering projects are slow to start as architecture solidifies, then fast to deliver as the build phase hits momentum. Hiring ramps are uneven because offer-to-start timelines vary.
The shape of your plan — how the target is distributed across time — is as important as the target itself. A realistic shape means your check-in data is meaningful: when you’re “on plan,” you’re genuinely on track. An unrealistic shape means your status indicators lie: you might be “behind plan” in week three even though you’re exactly where you should be, because the linear default expected progress that wasn’t possible yet.
The plan shape determines the signal quality of every check-in. Choose the wrong shape, and your status indicators become noise. Choose the right shape, and every check-in tells you something true about your trajectory.
The Six Core Shapes
While every plan is unique, most KR distributions fall into one of six recognizable shapes. Understanding these shapes helps you select the right starting point and communicate your plan logic to stakeholders.
1. Linear
Equal incremental targets across all periods. The simplest shape and the default in most tools.
-
Pattern: Week 1: 7.7%, Week 2: 7.7%, Week 3: 7.7% … Week 13: 7.7%.
-
Best for: KRs where effort and output have a constant, predictable relationship. Operational metrics like “reduce average ticket response time by 30 seconds” where process improvements are applied steadily.
-
Watch out for: Linear plans are rarely realistic for revenue, adoption, or project-based KRs. If you find yourself always behind plan in month one and catching up in month three, your KR isn’t linear — it’s back-loaded, and you should plan accordingly.
-
AI command: “Make it linear.”
2. Front-Loaded
Heavy early progress that tapers off. Most of the incremental target is concentrated in the first third of the period.
-
Pattern: Week 1–4: ~15% each. Week 5–8: ~5% each. Week 9–13: ~2% each.
-
Best for: KRs that depend on an early action whose effects diminish over time. Campaign launches, policy rollouts, one-time events that create initial momentum then require sustaining rather than growing. Also useful for churn-reduction KRs where interventions with at-risk accounts are front-loaded.
-
Watch out for: Front-loaded plans can create a false sense of security. If you hit 50% by week 4, it looks like you’re ahead — but the plan expected 60%. The tapering tail is easy to underestimate.
-
AI command: “Front-load the first month. Taper through Feb and March.”
3. Back-Loaded
Minimal early progress, with most of the target concentrated in the final third. The inverse of front-loading.
-
Pattern: Week 1–4: ~2% each. Week 5–8: ~5% each. Week 9–13: ~12% each.
-
Best for: KRs where the early weeks are setup, enablement, or infrastructure work that doesn’t produce measurable output until later. Engineering projects with an architecture phase. Sales KRs where pipeline takes 6–8 weeks to convert. Product KRs that depend on a mid-quarter launch.
-
Watch out for: Back-loaded plans carry risk concentration. If something goes wrong in month three, there’s no time to recover. Consider whether the back-loading is genuine (setup truly is required) or aspirational (we’re hoping things accelerate later without a specific reason why).
-
AI command: “Back-load into the last four weeks” or “Keep the first five weeks under 5% each, then ramp aggressively.”
4. S-Curve
Slow start, steep middle, gradual finish. The most common natural distribution for adoption-based and growth-based KRs.
-
Pattern: Week 1–4: ~3% each. Week 5–10: ~10–12% each. Week 11–13: ~4–5% each.
-
Best for: Product adoption metrics where early weeks involve onboarding and the middle weeks see organic growth. Revenue KRs where pipeline matures mid-quarter. Any metric that follows a “seed, grow, harvest” pattern.
-
Watch out for: The inflection point — where the slow start becomes the steep middle — is critical. If your plan says the ramp starts in week 5 but reality ramps in week 7, you’ll be “behind plan” for two weeks even though the S-curve is just delayed, not broken. Be prepared to shift the curve if the inflection point moves.
-
AI command: “S-curve. Slow start in January, steep ramp in February, tapering in March.”
5. Step Function
Flat periods punctuated by discrete jumps. Progress is not continuous but happens in identifiable events.
-
Pattern: Week 1–4: flat at 0%. Week 5: jump to 30%. Week 6–9: flat at 30%. Week 10: jump to 75%. Week 11–13: gradual to 100%.
-
Best for: KRs tied to specific deliverables or milestones. “Launch three features” where each launch is a discrete event. Integration projects where progress is binary (connected or not connected). Partner onboarding where each partner activation creates a step change.
-
Watch out for: Step functions are hard to track with continuous check-ins. Between steps, the status will be flat — which can look like stagnation even though the team is actively working toward the next jump. Annotate check-ins during flat periods to explain what’s happening under the surface.
-
AI command: “Flat at 0% through Jan, jump to 35% on Feb 3, flat until Mar 1, then ramp to 100%.”
6. Plateau and Ramp
Flat at a specific level for an extended period, then a sharp ramp to the target. A variant of back-loading with a deliberate hold period.
-
Pattern: Week 1–8: flat at 20%. Week 9–13: ramp from 20% to 100%.
-
Best for: KRs where you need to sustain a baseline before accelerating. Customer success KRs where the first two months are about holding retention at current levels while building the capability to improve it. Marketing KRs where the first phase is research and the second phase is execution.
-
Watch out for: The transition from plateau to ramp is a high-risk moment. If the ramp doesn’t start on time, the concentrated end-of-quarter targets become unachievable. Build a trigger: if the ramp hasn’t started by a specific date, modify the plan.
-
AI command: “Flat at 20% through February, then ramp to 100% across March.”
The Shape Selection Framework
Choosing the right shape starts with understanding the execution dynamics of your KR. Ask these three questions:
Question 1: Is progress continuous or event-driven?
If progress happens continuously (e.g., deals closing every week, bugs being resolved daily), choose a continuous shape: linear, front-loaded, back-loaded, or S-curve. If progress is tied to discrete events (feature launches, partner activations, campaign go-lives), choose a step function.
Question 2: Where in the quarter does the real work happen?
If the first month is setup or enablement and the real output comes later, choose back-loaded or plateau-and-ramp. If the first month is the highest-leverage period and the rest is sustaining, choose front-loaded. If effort is genuinely even, choose linear. If there’s a natural acceleration cycle (seed, grow, harvest), choose S-curve.
Question 3: What does last quarter’s actual data show?
This is the most underused question. If you ran a similar KR last quarter, look at the actual check-in data. Plot it. What shape did it follow? Your best predictor of this quarter’s distribution shape is last quarter’s actual pattern, adjusted for any known differences.
In Profit.co’s AI assistant, you can say: “Match last quarter’s actual check-in pattern.” Paste or upload last quarter’s data, and the AI will mirror the distribution shape with your new From/To range.
Quick Reference: Shape by KR Type
| KR Category | Common Examples | Typical Shape | AI Command |
|---|---|---|---|
| Revenue / Pipeline | Close $5M in new ARR; Generate 200 SQLs | S-curve or back-loaded | “S-curve across the quarter” |
| Product Adoption | Reach 10K active users; Achieve 80% feature adoption | S-curve | “Slow start, steep mid-quarter ramp” |
| Engineering Delivery | Ship 3 features; Reduce page load to <2s | Step function or back-loaded | “Flat until Mar 1, then jump to 70%, ramp to 100%” |
| Customer Success | Reduce churn to <3%; Increase NPS to 45 | Plateau-and-ramp or front-loaded | “Front-load January, taper through quarter” |
| Operational Efficiency | Cut ticket resolution by 30%; Automate 50 workflows | Linear or S-curve | “Linear” or “Slight S-curve” |
| Hiring / People | Hire 8 engineers; Complete 20 onboarding plans | Step function | “Steps: 2 hires Jan, 3 Feb, 3 Mar” |
| Marketing Campaigns | Drive 50K site visits; Generate 500 MQLs | Front-loaded or S-curve | “Front-load first 3 weeks, then taper” |
Modifying the Shape Mid-Quarter
The shape you choose at the start of the quarter is a hypothesis, just like the target. When execution data starts coming in, you may discover that the shape doesn’t match reality. Here are the three most common mid-quarter shape modifications:
1. Inflection Point Shift
Your S-curve assumed the ramp would start in week 5, but it’s now week 6 and the ramp hasn’t begun. The underlying pattern is still an S-curve — the inflection point just moved by one or two weeks.
The fix is simple: shift the curve without changing the target. Tell the AI: “Shift the ramp start to week 7. Compress the steep phase into weeks 7–11.” This preserves the overall target while aligning the distribution with the actual trajectory.
2. Shape Category Change
You planned a linear distribution but the first three check-ins show a clear S-curve forming. The early weeks were slower than linear, and week four showed a sharp acceleration. The shape category itself needs to change.
Tell the AI: “Convert to an S-curve. Fit the new curve to match my actual check-in data for weeks 1–4, then project the rest of the quarter.” The AI reads your existing actuals and generates a distribution that continues the observed pattern.
3. Tail Compression
You’re behind plan through the first half of the quarter, but the fundamentals haven’t changed — you still believe the target is achievable, just with a steeper back half. This is the most common modification: compressing what’s left into fewer weeks.
Tell the AI: “Keep actual values through today. Redistribute the remaining target equally across the final five weeks.” This preserves your history, acknowledges the slow start, and creates a realistic — if aggressive — path to the target.
The Shape Conversation: Aligning Expectations with Stakeholders
One of the most practical uses of plan shapes is in expectation management with stakeholders. When a director reports that their team is “15% behind plan in week four,” the natural response is concern. But if the plan is an S-curve where week four is supposed to be at 12% and the team is at 10%, the deviation is 2 percentage points — not 15.
The difference is the shape. A linear plan that’s at 10% in week four is 15 points behind. An S-curve plan that’s at 10% in week four is 2 points behind. Same actual result, dramatically different story.
This is why shape selection matters for communication, not just tracking. When you share a plan with your manager or your board, the shape sets the expectation for what “on track” looks like at any point in the quarter. A well-chosen shape prevents false alarms and ensures that genuine deviations are visible against the right baseline.
The shape is your narrative. A linear plan tells the story of steady progress. An S-curve tells the story of building momentum. A step function tells the story of discrete deliverables. Choose the shape that tells the true story of how your KR will progress — and your check-ins will confirm or correct that story with each data point.
Common Mistakes in Shape Selection
| Mistake | Consequence | Fix |
|---|---|---|
| Using linear as the default for everything | Early check-ins show red status for KRs that are actually on a normal trajectory. Teams lose trust in status indicators. | Take 60 seconds to ask: is this KR genuinely linear? If not, select the right shape upfront. |
| Back-loading as wishful thinking | Concentrating targets in month three without a structural reason. The team is just hoping things will accelerate. | Back-loading should be justified by a specific enabler: a launch date, a hire start, a campaign go-live. If there’s no enabler, the plan is aspirational, not realistic. |
| Over-fitting to last quarter’s data | Copying last quarter’s actual shape exactly, even though conditions have changed. | Use last quarter’s data as a starting point, then adjust for known differences (new hires, product changes, market shifts). |
| Ignoring the shape after initial setup | Setting a thoughtful S-curve at the start of the quarter, then never modifying it when the inflection point shifts. | Treat the shape as a hypothesis. When the first 3–4 check-ins suggest the shape is wrong, modify it. |
| Choosing a complex shape for a simple KR | Using an S-curve for a KR that’s genuinely linear, adding false precision to a simple trajectory. | If equal effort produces equal output each week, linear is correct. Don’t add complexity where it doesn’t exist. |
Shape your plans to match reality — not the other way around.
Profit.co’s AI assistant understands plan shapes: S-curves, back-loading, step functions, and more. Describe the shape you want in plain language and the plan table populates in seconds. Start your free trial.