Big initiatives don't fail at execution. They fail at the seam right before it.
A goal gets handed out. Everyone nods. And nobody has said out loud what they're depending on, who owns the ugly piece, or whether the timeline is real. Those unspoken things don't disappear — they resurface mid-execution, as a crisis instead of a question.
PlanningAlignment · the nod
ExecutionThe crisis · too late
35% vs 73%
Decisions imposed by edict are fully used 35% of the time — versus 73% when the people who own the work are brought in.
Source · Nutt 1999, Academy of Management Executive · 356 decisions
22 vs 14 mo
Imposed solutions take ~22 months to adopt versus ~14 for a discovery process — at roughly half the adoption rate.
Source · Nutt 2002, Why Decisions Fail
The launch everyone agreed to
The launch was approved. What it meant wasn't.
Illustrative scenario
The decisionLaunch the platform into APACShip by Q3Approved
Said itSaid halfNever said up
CEO
This is our year in APAC.
CFO
The unit economics work.
CPO
Yes — if scope holds.
Half‑saidScope never holds.
CTO
Doable on paper.
Half‑saidDoubts v2 is ready.
COO
I'll make it work.
Workstream leads · asked to own a slice
Eng lead
We'll try for Q3.
Half‑saidQ3 is not real.
GTM lead
Ready when product is.
Ops lead
Standing up support.
The floor · where the real state lives
Backend team
Migration's half done.
Known below · never asked
Platform team
v2 slips to Q4. Two workstreams built on it.
The top table approved Q3. The floor knew it was Q4 — nobody put the question to them.
The cost of the unowned
Every company has a decision nobody owns.And it is quietly costing them the year.
In plain terms
A cloud platform for organizational decisions that routes a goal to the people who own it and gets them to a committed answer — turning endless meetings and dead threads into one path to resolution.
What kind of thing
A cloud platform — for the decisions that cross teams and layers.
What it does
Routes a goal to the owners, and gets them to a committed answer — fast.
What it replaces
The endless meetings and dead email threads that never resolve.
How it works
A goal, routed to the people who'd own it — each giving one honest answer.
Someone puts a goal down with a real deadline. It routes to the owners. The chain assembles itself by recursion — nobody holds the whole map; each person handles their slice.
Nobody holds the whole map — each person handles their slice
Commit
I've got it. Owned, on the timeline.
Counter
I can — but not by then. Proposes a month.
Condition
I'll commit — if this holds. Names the risk.
Reroute
This is theirs, not mine. Hands it over.
Escalate
This needs a leadership call. Sends it up.
Five equal moves. None is the good button; none is the loud one — the honest answer is always the cheapest to give.
Sales → Pipeline owns it, on timeCommitted
Finance → Budget sign-off owns it, on timeCommitted
Eng → Platform v2 can't hit the date — two teams depend on itSurfaced now
The honesty linelucix does not tell you the answer. It makes sure the answer is made by the person who owns it, with what's true in the room, before the window shuts. The clean paths would've resolved anyway — the value is the ones that wouldn't.
The missing layer
The market already solved this. It hired a person to be the tool.
A Chief of Staff spends more time establishing who decides than deciding. They frame the question, find the owner, carry it to them, wait, chase, and bring the answer back. They are, functionally, a routing layer made of a human being.
The fastest-growing senior role of the last five years exists to do by hand the thing no software does. That is not a gap we're asserting — it's a gap the market has already priced, hired, and staffed.
150%
Growth in US Chief of Staff titles from 2015 to 2025 — triple the growth rate of comparable operator roles.
Source · LinkedIn Economic Graph Research Institute, March 2026
Three layers of software touch this problem. All three miss it — because each starts after the interesting part.
CommsChat · email · threads
Holds the message
Carries anything to anyone. Holds no model of who decides. Everything is a message; nothing is an ask with an owner and a date.
Task & PMTickets · boards · sprints
Holds the assignment
Assumes the decision is already made. A ticket is an instruction — these tools start after the interesting part.
Decision AIMeeting & notes tools
Holds the record
Captures what was decided. Retrospective by construction.
lucix
Holds the authority
Who has standing to answer this, and how it gets to them. Underneath the comms layer, before the task layer, ahead of the record.
The stack isn't missing a feature. It's missing a layer — and the market's current answer to a missing layer is to hire a person to be it.
No rollout required
It works where people already are.
The person who owns an answer never has to learn a new tool — or even log in. lucix meets them in email, renders as a first-class seam in Slack, and keeps one record underneath. Specified once, rendered everywhere.
EmailThe floor
Ask, answer, and commit straight from the inbox. A first-time responder needs no account — email is a designed surface here, not a fallback.
SlackThe seam
lucix reads and writes your channels so work stays in the open — but the decision never lives in a thread. Threads are I/O, never the record.
The platformThe record
One place every answer resolves and is signed into the record — whole on its own, the same truth however it was reached.
And it stops there
It decides and commits — then hands off.
Not a tracker, not a PM tool, not a system of record. Nothing to keep current, nothing to maintain. The discipline is the point — a scalpel, not a platform you have to feed.
Decide
lucix
Commit
lucix
Execute
Not us — on purpose
Track
Not us — on purpose
Maintain
Not us — on purpose
MT2R
Mean Time to Resolution — the number lucix is built to compress, from first raised to informed resolution.
Reopen rate · paired counter-metric
Did the resolution hold? Speed is the proxy; durability is the goal. We only ever report the two together.
Run enough decisions through it and a second map appears underneath — who really owns what, what actually depends on what. Not the org they drew; the org they have. A byproduct of decisions being made, never a thing anyone maintains.
Safe by design
A velocity tool people can trust — because of what it refuses to do.
Speed turns into surveillance the moment a tool starts scoring people or chasing them. lucix is built so it can't. These aren't settings you toggle — they're architectural: there is no object in the system that could do otherwise.
lucix never
Scores a person
Everything rolls up by team and state — never a per-person rate, ranking, or productivity score. There's no place one is stored, and no way to compute one.
lucix never
Nags anyone
Nothing decays if you ignore it. lucix may notice; it never chases. Pressure is always a person, reminders are always chosen, and silence is a valid answer.
lucix never
Shows an "on-track"
No percent-complete, no likelihood, no red-amber-green health. It projects the dates people volunteered as plain arithmetic — never odds, never a guess dressed as certainty.
lucix never
Leaks the watching
Who opened what, who's gone quiet, delivery trails — that never travels past the runner. The commitment moves to whoever needs it; the surveillance stays behind.
Who wins
Every company says "challenge assumptions."
lucix is where they finally can — safely, early, and on the record that matters. The rare product that wins at every level.
Leadership
Culture isn't a poster — it's whether the truth reaches you in time. The values they already claim, finally load-bearing. And the initiatives that matter actually resolve.
The floor
What makes people feel successful — and stay — is surfacing a real risk early, safely, and being heard. A legitimate, non-confrontational way to say "this timeline isn't real."
The Chief of Staff
Stops being the one who finds out at execution that it was never going to work. The map before the crisis, not after.
Why we're building this
Every team we've been on had one decision that quietly ran the year — and no software that could hold it. The tools we have move messages, tickets, and notes; none of them hold the thing that actually decides an outcome: who has the standing to answer, and whether they've truly said yes. So we're building the layer that does — and stops there. Not to replace the people who decide, but to make them impossible to ignore.
Nick Ashwin & Ryan Burrus Co-founders · lucix
Become a design partner
We're taking on a small number of design partners. Teams with a decision that keeps slipping — who want to shape lucix before anyone else has it.