Our Methodology

100 Days. Maximum Impact. How We Work.

From first discovery to live output — in a defined window. No months-long retainers. No endless strategy phases. A sprint model built for mid-market companies that need results, not reports.

01
Discover
Weeks 1–3
02
Define
Weeks 3–5
03
Design
Weeks 5–10
04
Deliver
Weeks 10–14

Why Most Consulting Engagements Fail to Deliver

Six months of discovery. A 200-slide deck. Three months of "stakeholder alignment." Another six months of "implementation planning." And then — something changes internally. The budget shifts. A new executive arrives. The project is deprioritized. The consultants are paid. Nothing ships.

This is not a hypothetical. It's the pattern that has made mid-market companies deeply skeptical of consulting engagements. Long timelines create too many opportunities for the world to change around you. Large teams create too many opportunities for the work to drift from what the business actually needs.

Redesign was built to break it. The 100-day sprint is not a marketing claim — it's a structural constraint that forces the right behaviors: scoping correctly, prioritizing ruthlessly, and delivering something real before organizational attention dissipates.

92%
of operations leaders say technology investments have not delivered expected value. The design gap — not the technology gap — is almost always the cause. Organizations invest in tools before designing the experience, process, or operating model those tools need to work.
Source: PwC, 2025
Why traditional engagements fail
Timelines extend until budget runs out, not until output is delivered
Scope expands without corresponding increases in clarity
Strategy phases become permanent because implementation is never started
Incentives are misaligned — billable hours reward time, not results

The Science Behind the Sprint Window

100 days is not arbitrary. It is the window in which organizational urgency is sustained, executive sponsor attention is held, budget isn't re-evaluated, and real output can be achieved — without cutting corners on research and design.

Shorter than 60 days and you're guessing. The research isn't done, the design isn't validated, and what you ship is an expensive hypothesis, not a solution. Longer than 120 days and the world changes around you: personnel shifts, strategic pivots, budget cycles — any of these can end a project that hasn't yet shipped.

100 days is the discipline that forces us to scope correctly, prioritize ruthlessly, and ship something real. It's a constraint we've chosen — and it makes the work better.

Under 60 days
Research is incomplete. Design isn't validated. You're shipping a guess.
60–100 days
The productive zone. Research complete. Design validated. Output achievable without organizational drift.
Over 120 days
Sponsors change, budgets shift, priorities evolve. The project becomes a relic before it ships.

Discover. Define. Design. Deliver.

Four phases. One output. The most expensive mistake in consulting is solving the wrong problem with precision — so each phase builds on the last, with explicit outputs that gate the next.

Phase 01
Discover
2–3 weeks
Deep research into customers, markets, and context. Customer interviews, competitive analysis, data review, and stakeholder alignment. We don't skip this — because the most expensive mistake in consulting is solving the wrong problem with precision. Discovery is the insurance policy that makes everything else work.
Output: A research synthesis and insight brief — a documented set of findings, patterns, and hypotheses that define what we're solving and why it matters. Shared with your team before we move to Define.
Phase 02
Define
1–2 weeks
Frame the right problem using the Stacey Matrix — is it complex, complicated, or obvious? Complex problems require experimentation and learning loops. Complicated problems require expertise and structured process. Obvious problems require standardization. Applying the wrong solution type to the wrong problem type is how projects fail. Define creates the brief that everything else is built from.
Output: A problem statement, a set of design criteria, and a sprint brief — agreed by both teams before a single solution is designed. This brief is the scope. Scope changes go through this document.
Phase 03
Design
4–6 weeks
Co-create solutions through workshops, prototyping, and validated experiments. For CX engagements: journey maps, NPS program architecture, and operational playbooks. For product engagements: research synthesis, wireframes, prototypes, and user testing. For business design: GTM models, service blueprints, and business model frameworks. Every design artifact is validated before it becomes a recommendation.
Output: Validated design concepts and a prioritized implementation plan — not a presentation of options, but a documented recommendation with evidence and a sequenced execution brief.
Phase 04
Deliver
3–5 weeks
Implement end-to-end within the sprint window. For product work: production-quality code, design systems, and a documented handover that your team can maintain. For CX and business design: implemented programs, trained teams, and a 90-day operational roadmap with ownership clearly assigned. We stay until something is live — not until the deck is done.
Output: Live impact — not a presentation. A functioning product, an operating CX program, an implemented business model, or a trained team with a documented playbook. Something that didn't exist 100 days ago.

What You Get at the End

Every sprint produces six core deliverables — regardless of practice area. These are the structural commitments we make at the start of every engagement.

Defined, prioritized problem statement
Agreed between your team and ours before design begins
Validated design output
Prototype, journey map, or business model — tested with real users or customers
Implementation-ready documentation
Your team can execute without us in the room
90-day roadmap with ownership
Who does what, by when — not just a list of next steps
US-based project team for the full sprint
Same team, start to finish — no handoffs mid-sprint
Weekly progress reviews and final readout
No surprises. You see the work as it develops, not at the end.

A Sprint That Fits Mid-Market Budget

Enterprise-grade methodology at a cost structure designed for mid-market companies. The sprint model delivers results at 40–60% lower cost than comparable Big 4 or MBB engagements — because it's designed for focus, not billable hours.

Diagnostic Sprint
$75K – $150K
A rapid 4–6 week diagnostic of your CX program, product, or business model. Produces a clear brief, a diagnosis, and a set of prioritized recommendations. The right entry point when you need to understand the problem before committing to a full sprint.
Enterprise Program
Custom
Multi-sprint programs for organizations running parallel initiatives across CX, product, and business design. Structured as a series of 100-day sprints with a shared strategic framework. Pricing reflects scope and duration — contact us to discuss.
How we compare
Big 4 / MBB $500K – $2M+ entry
Peer boutiques $200K – $500K typical
Redesign $75K – $400K · Fixed scope · Fixed timeline
Not sure where to start?
2-Week Diagnostic — $15K–$25K
A rapid assessment of your CX program, product, or business model that produces a clear brief for the sprint. Includes stakeholder interviews, competitive context, and a prioritized problem statement. The diagnostic fee is credited against the full sprint if you proceed within 60 days.
Start with a diagnostic

The sprint format also bypasses long procurement cycles — it's scoped and time-bounded, which means it can often enter the vendor system as a project rather than a retainer. This reduces procurement friction significantly for mid-market organizations with defined vendor management processes.

Common Questions About the Sprint

Can we run a sprint in parallel with our internal roadmap?
Yes — and that's the point. The sprint is designed to run alongside your existing operations, not disrupt them. We embed into your team's rhythm: attending relevant internal meetings, working within your tooling, and adapting our review cadence to your calendar. The sprint produces output that feeds your roadmap — it doesn't compete with it.
What if the scope changes during the sprint?
Scope changes are managed through the Define phase. Once the sprint brief is agreed — by both teams — we manage change through a structured process. Adding scope means adjusting the timeline or removing another scope item from the brief. We don't do open-ended engagements. The brief is the contract. Changes to it are decisions, not discoveries.
Do you work remotely or on-site?
Both. New York-area clients typically work in a hybrid model — remote for day-to-day progress, in-person for workshop milestones. For US clients outside the New York area, we run remote by default with planned in-person sessions at sprint kickoff, the Define workshop, and the final Deliver readout. International clients work fully remote with timezone-adjusted cadence.
What if we don't know exactly what we need?
Start with a 2-week diagnostic — a rapid assessment of your CX program, product, or business model that produces a clear brief for the sprint. The diagnostic includes stakeholder interviews, a competitive context review, and a prioritized problem statement. Entry cost: $15K–$25K. The diagnostic fee is credited against the full sprint if you proceed within 60 days. If the diagnostic concludes that a sprint isn't the right tool, we'll tell you that too.
Who from your team works on the sprint?
The same team, start to finish. We don't hand off between a "strategy team" and a "delivery team." The people who do the discovery are the people who design the solution and oversee delivery. This is intentional — knowledge transfer between phases is where most consulting engagements lose fidelity. We keep the team intact for the full 100 days.
What happens after the sprint ends?
The 90-day roadmap produced in the Deliver phase gives your team a clear set of actions with ownership assigned. For clients who want continued support, we offer a post-sprint advisory arrangement — a lightweight monthly cadence to review progress, unblock issues, and plan the next sprint if needed. This is offered as a separate engagement, not bundled into the sprint cost.

Services That Use the Sprint Model

The 100-day sprint is the delivery model across all Redesign practices. Every engagement — regardless of practice area — is scoped, structured, and delivered within the sprint framework.

Every Sprint Begins With a 30-Minute Call

We'll ask about your problem, your timeline, and your team. You'll ask about our approach and our references. If it's a fit, we'll send a sprint brief within the week. No commitment required to have the conversation.

Start the conversation →

Frequently Asked Questions

What is the 100-Day Sprint? +

A time-boxed consulting engagement that moves from first insight to live impact in 100 days. It follows four phases — Discover, Define, Design, Deliver — and ends with a shipped output, not a report. The 100-day constraint is a hard limit, not an estimate.

Why 100 days specifically? +

Long enough to do real research and design work. Short enough to maintain urgency and prevent scope creep. 100 days creates a clear delivery milestone that organizations can plan around and measure against.

What can realistically be delivered in 100 days? +

A validated product or service design, a CX program with operational loops, a GTM strategy with a defined sales motion, or a functioning MVP. The scope is scoped to fit — not everything needs to be in the first sprint.

How is the 100-Day Sprint different from an agile sprint? +

Agile sprints are two-week development cycles within a defined product. The 100-Day Sprint is an end-to-end consulting engagement — from problem definition through research, design, and live delivery. It uses sprint discipline without being limited to software development.

What does a 100-Day Sprint cost? +

Entry engagements start at $75K for a diagnostic sprint. Full 100-day engagements run $150K–$400K depending on the scope, team size, and the complexity of the problem being solved.