Right-Sized Framework™

Chapter 1

Stuck in the Mud with No Traction

You can feel a capable team working harder every week while progress quietly slips. The issue isn't talent — it's the system. This chapter is the turning point.

Step InsideTake the AssessmentJump to References
Whiteboard planning with sticky notes

Step Inside

I've been there.

Watching a capable team work harder each week while progress quietly slips. Plans expand. Dependencies multiply. Confidence erodes. Not because the team lacks talent — but because the system isn't supporting the work.

I know that pain. And more importantly, I can show you a better way forward.

The Right-Sized Framework is a practical approach to escaping chaos without burying teams in bureaucracy. It was shaped through wins and hard lessons across aerospace, defense, and advanced technology programs — where the difference between success and failure was rarely the idea. It was the system that connected vision to delivery.

At its core is a six-phase product development cycle:

  • Product–Market Fit ensures you are solving a real problem
  • Plan aligns teams around achievable direction
  • Design turns intent into executable solutions
  • Build converts effort into working capability
  • Test exposes risk before it becomes failure
  • Release delivers value and informs the next cycle

Each phase exists for a reason. Together, they create momentum instead of friction.

If you recognize overbuilt MVPs, meetings without clarity, and schedules that slip quietly, this chapter is your turning point. You will see how to right-size rigor, establish a fast and sustainable cadence, and align leaders, engineers, and customers around measurable outcomes.

Action Plan

Four moves that change the trajectory.

Diagnose & learn

  1. Take the RSF Assessment. Identify where your organization is performing well and where structural constraints are limiting progress.
  2. Read the Book. Build a clear understanding of the framework, its intent, and how each phase connects vision to execution.
Team brainstorming with colorful notes — vision to MVP, turning clarity into motion.
Blueprints and laptops around a table — systems thinking, interfaces, integration.

Directed Tools & Templates

Apply the framework this week.

Every chapter ships with tools you can put to work immediately. Start with whichever matches where you are right now.

Executive Product Development Assessment

Right-Sized Framework Executive Self-Assessment

Most organizations do not struggle because they lack intelligence or effort. They struggle because one structural dimension is quietly constraining velocity. This assessment helps you identify that constraint.

You can also take this at www.rightsizedframework.com/RSFassessment.

1 = Never true · 2 = Rarely · 3 = Sometimes · 4 = Often · 5 = Consistently — answer honestly. This is a mirror, not a report card.

Hands-on electronics build and test on a bench.
Section 1: Product–Market Fit (PMF) Total possible: 35

1. Our product vision is grounded in validated customer needs.

2. We clearly define our target customer before major development begins.

3. We test concepts with real customers prior to full investment.

4. Sales, marketing, and engineering share a unified value proposition.

5. We validate demand before scaling development or production.

6. Customer feedback directly influences product decisions.

7. We track engagement, adoption, and retention metrics.

Section 2: Program Leadership & Execution Total possible: 35

8. Leadership sets clear priorities aligned with strategy.

9. We maintain a disciplined monthly rhythm that drives predictable progress.

10. Risks are identified early and actively managed.

11. Scope changes are controlled and deliberate.

12. Budget and schedule estimates are realistic.

13. Cross-functional communication is clear and consistent.

14. Projects meet milestones without recurring crisis behavior.

Section 3: Systems Engineering Discipline Total possible: 35

15. System requirements are defined clearly before development.

16. We maintain traceability from need through test.

17. Integration is planned early, not left to the end.

18. Entry and exit criteria are defined for major reviews.

19. Verification and validation occur before release.

20. Technical risk is systematically assessed and consciously reduced.

21. Modeling and analysis are used appropriately without bureaucracy.

Section 4: Design & Build Effectiveness Total possible: 25

22. We prototype and test early.

23. Design revisions are driven by data, not opinion.

24. Engineering collaborates effectively with adjacent functions.

25. Our development cycle follows structured phases and review discipline.

26. Rework is identified early and does not cascade into late crises.

Section 5: Metrics & Release Readiness Total possible: 25

27. We use leading and lagging metrics to measure real progress.

28. Metrics are reviewed regularly and drive decisions.

29. Release decisions follow defined quality criteria.

30. Internal teams are trained before launch.

31. Customers can achieve value quickly after release.

References & Further Study

Go Deeper

  • book
    The Lean Startup

    Eric Ries

  • book
    Inspired: How to Create Products Customers Love

    Marty Cagan

  • book
    Good to Great

    Jim Collins

  • book
    Measure What Matters

    John Doerr

  • book
    Scrum: The Art of Doing Twice the Work in Half the Time

    Jeff Sutherland

  • book
    The Hard Thing About Hard Things

    Ben Horowitz

  • article
    NASA Systems Engineering Handbook
  • video
    The Knowledge Project
  • video
    Masters of Scale