37signals-way

Structure lean product development with fixed-time cycles and shaped pitches.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/fsolla/teqo --skill 37signals-way-fsolla
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 37signals-way
Source: https://github.com/fsolla/teqo/tree/main/.agents/skills/37signals-way
Command: npx skills add https://github.com/fsolla/teqo --skill 37signals-way-fsolla

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the common pitfalls of software development, such as feature bloat, endless backlogs, and burnout, by providing a framework for building high-value products with small teams and fixed constraints.

Core Features & Use Cases

  • Shaping Work: Transform raw ideas into bounded, actionable pitches that leave room for creative execution.
  • Betting & Cycles: Replace infinite backlogs with six-week betting cycles to maintain focus and urgency.
  • Opinionated Defaults: Learn to prioritize simplicity and clear communication over endless user preferences.
  • Use Case: Use this framework when your team is struggling with scope creep, long-term roadmaps that never ship, or the feeling that you are building too much for too little impact.

Quick Start

Apply the 37signals way to evaluate our current product roadmap and identify which features we should cut to ship our next release in six weeks.

Frequently Asked Questions about 37signals-way

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop scope creep and feature bloat in lean product development?

To stop scope creep in lean product development, you apply fixed-time cycles and shape raw ideas into bounded pitches. This framework eliminates infinite backlogs by limiting work to six-week betting cycles, ensuring small autonomous teams ship high-value features without burnout.

What is the best way to prioritize a product roadmap for a small autonomous team?

The best way to prioritize a product roadmap for a small autonomous team is to replace long-term plans with opinionated defaults and six-week betting cycles. By shaping work into bounded, actionable pitches, teams focus on simplicity and predictable, high-quality software delivery.

How does the Shape Up method work for fixing time and building less software?

The Shape Up method works by fixing time and building less software through a structured framework of shaping work, betting, and cycles. It transforms raw ideas into bounded pitches, eliminates backlogs, and uses fixed-time cycles to maintain focus and urgency for small teams.

When should I use fixed-time cycles instead of traditional agile backlogs?

You should use fixed-time cycles instead of traditional agile backlogs when your team struggles with endless task lists, scope creep, or never-shipping roadmaps. This approach replaces infinite backlogs with six-week cycles to maintain focus, urgency, and predictable software delivery.

Can I apply the 37signals philosophy to evaluate and cut features from an existing product roadmap?

You can apply the 37signals philosophy to evaluate and cut features from an existing product roadmap by shaping remaining ideas into bounded pitches and adopting six-week betting cycles. This framework helps identify low-value features to eliminate, ensuring your next release ships predictably.