NCT for Engineering Teams
Give your engineers the 'why' behind every ticket. Less context-switching, better decisions, and a direct line from the code they write to the strategy it serves.
Sound familiar?
The problems NCT was built to fix
Problem 1
Developers are closing tickets, but something still feels off
Velocity looks fine. Sprints are shipping. But the product isn't moving in any particular direction. That's what happens when the work is disconnected from the problem — individually correct, collectively aimless.
Problem 2
'Why are we building this?' is a question you dread
Not because the answer doesn't exist, but because it lives in a Notion doc from Q2 planning that nobody has read since. The person who knows the why is in a meeting. The engineer waiting needs to ship.
Problem 3
Tech debt Narratives never survive prioritization
When everything is a ticket with no story behind it, refactors and reliability work compete on equal footing with features — and features win every time. Technical work needs narrative too.
How it works
Three layers — built for engineering teams
Every layer of NCT maps directly to how engineering teams already think about their work.
Every piece of engineering work now has a customer problem attached to it. Engineers can read the Narrative and understand, in plain language, why this cycle matters.
Commitments are engineering contracts, not stretch goals. Your team commits to delivering them — and the definition of done is clear upfront.
Your existing sprint tasks, PRs, and reviews — now organized under the Commitment they serve. Nothing changes about how you work, only the visibility.
Real example
A Narrative for engineering teams
"Our CI pipeline takes 18 minutes on average. Developers are context-switching during the wait, losing flow, and shipping slower as a result. Our best engineers are most affected because they're iterating fastest. If we get CI under 5 minutes, we expect measurable improvements in shipping frequency and developer satisfaction."
Commitments for this Narrative:
- 1Audit and parallelize the three slowest CI pipeline stages
- 2Migrate test suite to run against a dedicated test DB instead of shared staging
- 3Add pipeline caching for node_modules and build artifacts
Use cases
How engineering teams use NCT
Engineering-led initiatives
Write a Narrative for tech debt or reliability work. "Our background job failures are causing data inconsistencies that erode trust for power users." Now it's a strategic bet, not a ticket.
On-call and incident reduction
Run a Narrative around system reliability. Commitments become the specific changes your on-call team commits to — with measurable intent behind them.
Platform and infrastructure work
Infrastructure work without a Narrative gets cut. Infrastructure work with a Narrative — tied to a real customer impact — survives roadmap reviews.
Reducing interruptions mid-cycle
When a stakeholder asks for something mid-sprint, the active Narratives are the answer: 'That's not part of our current cycle. Here's what we committed to and why.'
“For the first time, our engineers can explain to anyone — including themselves — why a ticket exists. That's not a small thing.”
— Engineering Manager, Developer tools startup
See NCT in action
Example NCTs for engineering teams
Reducing CI Pipeline Time
Cut CI build times from 18 minutes to under 5 minutes to restore developer flow and increase shipping frequency.
Product & EngineeringEnterprise API Rate Limiting
Redesign API rate limiting to serve enterprise customers without impacting the reliability of the platform.
Infrastructure & PlatformMigrating a Monolith to Microservices
Decompose a monolithic application into services to improve team autonomy, scalability, and deployment speed.
NCT works across the whole company
Product →
Stop explaining your roadmap in slides. Let your Narratives speak for themselves
Marketing →
Connect your campaigns to the customer problems they solve
Sales →
Stop tracking activity, start tracking intent. NCT gives sales teams a framework for connecting territory strategy to the actual deals and conversations that close business.
Also works for
Startups →
You don't need a planning department
Scale-Ups →
You've outgrown the founder's whiteboard but you're not ready for enterprise process. NCT gives growing teams alignment without the bureaucracy that slows you down.
Enterprise →
Replace your OKR spreadsheets with a framework that actually connects strategy to execution. NCT gives large organizations the structure they need without the bureaucracy they're trying to escape.
Remote Teams →
When you can't align in the hallway, you need alignment in the system. NCT gives distributed teams a shared strategic context that works across time zones
Founders →
Stop being the single point of failure for strategic context. NCT helps founders get the strategy out of their head and into a system that the whole team can execute on.
Ready to run NCT with your engineering teams?
Set up your first cycle in minutes. Free forever to start — no credit card, no consultant.
Free forever. No credit card needed.