{{ description }}
+| + {{ header }} + | +
|---|
| + + | +
+ Common ways teams fail at BEAT—and how to fix them. +
+Signs the methodology isn't serving the team:
++ Discuss in Beat Close. Adapt the framework. BEAT is a tool, not a religion. If it's not working, change it or choose something else. +
+Know your context. Adapt accordingly.
++ The principles guide us. The framework implements them. +
+We recognize three roles, loosely held.
+{{ role.description }}
++ We work in beats—flexible iterations of one to two weeks. +
+Review priorities and pull initial work
+Check in async daily, work autonomously
+Reflect: what worked, what didn't, what to improve
++ + Beats have goals, not commitments. We aim; we do not promise. There is no sprint pressure, no velocity tracking, no burndown theater. +
+Documentation effort scales with task size.
+{{ item.description }}
++ We size with S/M/L, not story points. We do not groom. We do not point. We do not track velocity. +
+We use four buckets to organize work.
+{{ bucket.description }}
+A simple kanban with priority built in.
+3 items per maker
+Pull from top
+Return to backlog after 5 days
++ Balanced. + Empowered. + Async. + Teams. +
+ +
+ A software delivery methodology built for how developers actually work.
+
+ Created by Lukasz Raczylo.
+
+ We are uncovering better ways of building software by doing it and helping others do it. +
++ BEAT emerges from research on how developers actually work. We built it for these realities, not against them. +
+ +Deep dive into each aspect of BEAT
+{{ card.description }}
+We will not interrupt sacred time. We will wait.
+We will write first, meet only when writing fails.
+We will provide goals, not instructions. Constraints, not control.
+We will cut scope before we cut rest. We will plan for humans.
+We protect focus.
+We write things down.
+We trust each other.
+We work sustainably.
+We ship and learn.
++ BEAT: Built for how developers actually work. +
++ BEAT v1.0 by Lukasz Raczylo +
++ When someone new joins a BEAT team, here's how to get them up to speed. +
+By the end of the first month, new members should:
+{{ item }}
++ The Connector (or Enabler if no Connector) ensures: +
++ Onboarding should feel like a gradual ramp, not a firehose or an abandonment. +
++ How we work day-to-day: meetings, collaboration, incidents, and technical practices. +
+Hard limits protect our time.
+{{ ceremony.purpose }}
++ + If a topic needs more than one hour: write first, comment async, meet on the delta. Never extend. +
+Replace standups with written updates.
+Default mode is solo deep work.
++ We do not schedule pairing. We do not mandate walkthroughs. We do not assign buddies. Collaboration is initiated by those who need it. +
+Work is not done until it meets these criteria.
++ + The team owns this definition. Adjust it as needed. But once agreed, honor it. "Done" means done—not "done but..." or "done except..." +
+When production breaks, normal rules suspend temporarily.
++ + This is not normal work. Incidents should be rare. If they're frequent, that's a systemic problem to solve—not a reason to abandon sustainable pace. +
+Optional practices that align well with BEAT principles.
+{{ practice.description }}
++ These are not mandated. They are offered as practices that support focus, speed, and quality. Adopt what serves you. Discard what doesn't. +
++ Guiding principles organized into four categories: Focus, Communication, Autonomy, and Sustainability. +
++ {{ principle.description }} +
++ Everything you need at a glance. Print this page and keep it handy. +
++ BEAT v1.0 by Lukasz Raczylo +
++ Attribution appreciated. Improvement welcomed. Dogma discouraged. +
++ The foundation of everything we do. What we value in our work and how we treat each other. +
++ While there is value in the items on the right, we value the items on the left more. +
++ over {{ value.over }} +
++ Beyond what we value in our work, we hold these values in how we treat each other. +
++ {{ value.description }} +
++ These values are not just words on a page. They guide our daily decisions, how we interact with each other, and how we approach every piece of work. When in doubt, return to these values. +
+