Core Pillars of FLOQ

Five foundational principles that replace the sprint-based model with continuous, outcome-driven flow.

1

Ship Continuously

The unit of delivery is the feature, not the sprint. When something is ready, it ships. A feature completed at 2:00 PM is live by 2:30 PM.

❌ Old WayWork batched into 2-week sprints. A feature ready on Day 2 waits until Day 14 for review and release.
✅ FLOQ WayFeature is done? It ships immediately. The cost of deployment is near zero. The cost of delay is what kills you.
2

Unblock Ruthlessly

Every blocker is treated as a Floq Emergency. Zero tolerance for idle time. Decision-makers are pulled in within 30 minutes.

❌ Old WayDeveloper blocked. Mentions it in tomorrow's standup. Scrum Master logs it. Three days lost.
✅ FLOQ WayAI agents attempt automated resolution. If unresolved, Floq Lead notified immediately. Decision made within 30 minutes.
3

Respond to Real Outcomes

The only metric that matters is Outcome Impact — did the thing we shipped move the business metric it was supposed to move?

❌ Old WayTeams measure "velocity" — story points completed. 80 points of features no customer uses = celebration.
✅ FLOQ WayFeature didn't move its target metric within the Pivot Window? The team pivots immediately. No hiding behind points.
4

Generate with AI

AI is a team member, not a tool. The human role shifts from "code writer" to "outcome architect."

❌ Old WayAI is a "tool" — a fancy autocomplete. The process doesn't change. Human writes every line.
✅ FLOQ WayArchitecture: Human-led, AI-informed. Code generation: AI-led, Human-reviewed. Testing & docs: AI-driven.
5

Evolve by Signal, Not Schedule

The team evolves in response to signals, not calendars. The default state is building.

❌ Old WayEvery 2 weeks: "What went well?" — regardless of whether anything meaningful happened.
✅ FLOQ WayDeployment failure → immediate Floq Retro. Metric miss → Pivot Session. No signal? No meeting.