The First Homily of the Church of Sequential Decision Systems
On diagnosis · The seeing problemBrothers and sisters, we have a problem.
Not a data problem. Not a talent problem. Not a tools problem.
A seeing problem.
The organizations of this world are drowning in dashboards and starving for decisions. They have hired armies of analysts. They have purchased platforms. They have run workshops. They have aligned stakeholders. They have built, Lord help them, centers of excellence.
And still they ask the wrong question.
They walk into the room and they say: what does the data tell us?
And I am here to tell you, on this day, that the data tells you nothing. The data sits there. Patient. Indifferent. Waiting for someone to ask it something worth answering.
You have to bring the question.
That is Step One. That has always been Step One. And for fifteen years, an entire industry looked at Step One and said, we'll come back to that, and went straight to Step Four, and built something, and shipped it, and measured it, and called it transformation.
We know what happened next.
We have all been in that meeting.
The way is not complicated. It was never complicated. It only feels complicated because we were taught to fear the silence before the spreadsheet opens. We were taught that uncertainty is a gap to be filled with data, not a structure to be named and worked.
The way is this:
Name the decision. Frame the problem. Design the solution. Source the data. Build the thing. Return to the beginning.
Six steps. A cycle. Not a project plan. Not a methodology deck. A discipline. Something you do until it becomes the way you see.
This is what we preach.
Not because it is new. Warren Powell did not discover something new. He named something ancient: that every consequential choice has a structure, and that structure can be revealed, and that revealing it before you act is the entire game.
The heretics will tell you speed is the virtue. That you iterate your way to clarity. That done is better than defined.
We do not cast them out. We pray for them.
We have seen what they build.
If you are here, you already felt something was wrong. You sat in the room where they announced the model was ready and the question still had not been asked. You watched the dashboard go live and watched the decisions stay the same.
You are not crazy.
You are just early.
The Decision Factory is our text. Not because it has all the answers. Because it asks, chapter by chapter, the question that keeps getting skipped.
What are we actually trying to decide?
Go now. Take it back to your organizations. Ask the uncomfortable question before the data loads. Sit in the silence.
That silence is not emptiness.
That is where the work begins.
The Second Homily of the Church of Sequential Decision Systems
On confession · What we did before we knew betterI want to confess something on behalf of all of us.
We loved the data.
We did. We were not innocent. When the platforms came, when the warehouses filled, when the dashboards bloomed across every wall of every operations center in every company that could afford the software, we were there. We believed. We thought: this is it. This is the thing that changes everything.
We were so sure the answer was in there somewhere.
We just had to look harder. Query better. Visualize differently. Hire someone who understood Python. Hire someone who understood the business. Hire someone who understood both. Run the model again. Slice it another way.
And somewhere in that decade, quietly, without anyone calling a meeting about it, the question got lost.
Not deleted. Not rejected. Just... skipped.
Because the data was right there. And the question was hard. And the stakeholders were impatient. And the quarter was ending. And we had a tool that could produce an answer in forty-five seconds, and we had a decision that needed to be made, and it felt close enough.
It was not close enough.
I am not here to condemn the analysts. They were handed a hammer and told to fix the house and nobody told them what was wrong with it.
I am here to name what was lost.
The decision. The actual, specific, consequential choice that someone in that organization needed to make, that would change something real, that had a cost if made badly and a payoff if made well. That thing. The thing that should have been written at the top of the page before anything else. The thing that would have told you which data mattered and which data was just noise dressed up in a pivot table.
That thing was skipped.
It is still being skipped.
In your organization, right now, there is a team three weeks into a project that has not yet written down what decision they are supporting. They have a timeline. They have a Jira board. They have stakeholder alignment. They have access to the data warehouse.
They do not have a decision frame.
They will deliver something. It will be real and it will be expensive and it will be used in a presentation and then it will age quietly in a folder until someone asks why nothing changed.
This is not a technology problem.
This is a liturgical problem.
We forgot the order of the service. We started with the offering before the invocation. We skipped the scripture and went straight to the collection plate.
The order matters.
Name the decision first. Frame what you are optimizing, what you are trading, what success looks like before the model runs. Do the hard slow work of sitting with the problem before you solve it.
Step One is not a formality.
Step One is the whole thing.
Everything else is just evidence.
Go back. Go all the way back. I know the timeline is tight. I know the project is already in flight. I know someone has already promised something to someone.
Go back anyway.
That is not failure. That is the discipline.
That is what we practice here.
The Third Homily of the Church of Sequential Decision Systems
On parable · The bridge to nowhereLet me tell you about the man who built the perfect bridge.
He spent two years on it. The engineering was immaculate. The materials were sourced well. The team was skilled and the project came in under budget, which never happens, and everyone celebrated, and the photos were good, and the case study was written.
The bridge connected the north side of the valley to the south side of the valley.
No one lived on the north side.
No one had ever lived on the north side.
There was no road on the south side that led anywhere the north side needed to go.
The bridge was perfect. The bridge was correct. The bridge was, by every internal measure of bridge-building, a success.
And it connected nothing to nothing, beautifully, on time, under budget, forever.
I have seen this bridge. You have seen this bridge. Some of you have built this bridge. Some of you are building it right now, and the ribbon cutting is in Q3, and the slides are already drafted.
We do not build bridges here.
We ask first: where does someone need to go? What is stopping them? What would change if that barrier were removed? Who decides? What do they need to believe to act differently?
Only then do we reach for the steel.
This is not caution. This is not slowness for the sake of slowness. The organizations that practice this discipline do not move slower. They move with less waste. They build fewer perfect bridges to nowhere. They spend the same energy and arrive somewhere that matters.
The enemy is not complexity.
The enemy is not bad data.
The enemy is the moment, early in every project, when the room is full of smart people and someone opens a laptop and pulls up the dataset and everyone orients toward the screen and the question, the actual question, the question that should be on the whiteboard in large letters before anything else happens, floats up and away and is never spoken.
That moment has a name.
We call it the skip.
The skip feels like progress. The skip has the energy of action. The skip produces artifacts: queries, models, visualizations, decks. The skip is comfortable because it moves and motion feels like work and work feels like value.
The skip is how you build the bridge to nowhere.
The antidote is not a framework. Frameworks can be skipped too. We have watched people fill out the problem framing template while skipping the problem framing.
The antidote is a posture.
It is the willingness to be the person in the room who says, before the laptop opens, before the data pulls, before the model runs: wait. What are we deciding? Who decides it? What would have to be true for them to decide differently?
That person is uncomfortable to be.
That person saves the project.
We are training that person. That is the entire ministry. Not the tools. Not the methods. Not the six steps, though the six steps matter. The person who has practiced the posture long enough that it is no longer brave to ask the question. It is just what they do.
It is just how they see.
Somewhere right now, a team is three weeks from launch on a model that will be technically correct and operationally useless, and one person in that team has a feeling, a quiet nagging sense that something upstream was never resolved, and they are deciding whether to say something.
Say something.
The bridge is not worth finishing if it goes nowhere.
Go back to the beginning.
Ask the question that should have been asked first.
That is the whole gospel.
That is all we have ever preached.