Durable performance in organizations and markets. Creator, Performance Architecture™ | Energy, technology and capital markets at @farmcreek.
Kennebunkport, Maine
- Tweets 900
- Following 1,856
- Followers 384
- Likes 492
Pinned Tweet
Most people try to improve performance by increasing effort.
That works—until it doesn’t.
Because performance, at scale, is not a function of effort.
It’s a function of architecture.
I wrote this to explain why:
open.substack.com/pub/ericbl…
5
7
299
A decision should not reopen because someone is uncomfortable with it.
It should reopen because something material changed.
Define that condition when you make the decision.
#performancearchitecture #leadership #decisionmaking
7
The org chart tells you where authority is supposed to sit.
Repeated decision paths tell you where the organization believes it actually sits.
Watch where difficult decisions travel.
That is the real authority map.
1
19
Your org chart shows where authority was assigned.
Your decisions show where it actually lives.
Watch where the difficult ones travel.
14
For Eric, I’d keep it tight and reinforce today’s Performance Architecture theme:
AI can make the work faster.
It cannot make the organization decide.
That is why AI will expose operating-model problems faster than it solves them.
Faster answers make slow architecturevisible.
16
A reconciliation needed once may be a control.
A reconciliation needed every Friday may be a diagnostic.
What keeps getting reconciled because the underlying system never closes?
16
Recurring reconciliation is often the invoice for architecture nobody fixed.
Don't start by eliminating the meeting.
Ask why the organization has to keep purchasing alignment with human time
1
15
Commander's intent solves an organizational problem far beyond the military:
How do you push authority toward information without losing alignment?
Delegate the decision.
Preserve the intent.
17
Instead of asking only:
“Was it a good decision?”
Ask:
Where in the Decision Journey did the system strengthen or weaken it?
Different question. Much better diagnosis.
18
A decision doesn't begin when someone chooses.
Signal → framing → evidence → challenge → authority → decision → commitment → execution → observation → outcome → learning.
The decision is a transition point.
Not the whole system.
1
25
Management attention is capital.
If senior leaders repeatedly resolve work that should close lower in the organization, management capacity is being used as operating infrastructure.
That is an architecture tax.
17
our actual priorities are not the items on the strategy slide.
They are the things allowed to displace everything else.
Teams learn that hierarchy very quickly.
24
Every new priority reprices the work already underway.
Leaders often miss this because the new request takes five minutes to make.
The organization pays the switching cost.
Before adding another priority:
What stops so this can start?
16
One question worth taking into Friday:
What work required someone more senior than the work itself should have required this week?
That is not just a productivity question.
It is an operating-system diagnostic.
16
Management attention is capital.
Every recurring follow-up consumes it.
Every unnecessary escalation consumes it.
Every broken handoff consumes it.
Every decision that has to be remade consumes it.
Follow where attention repeatedly goes.
You will find architecture below
10
dd two measures after the next meaningful disruption:
Recovery Time.
Then add a second:
Recovery Cost.
Not dollars.
Escalations. Meetings. Exceptions. Senior attention. Heroics.
The second number tells you whether the system recovered or the people compensated for it.
12
Most organizations measure whether performance recovered.
Few measure what recovery required.
Three days of recovery through designed resilience is not equivalent to three days powered by five exceptional people working until midnight.
Same dashboard.
Different architecture.
9
Every escalation contains information.
Sometimes the decision genuinely belongs upstairs.
Sometimes the organization has simply learned that escalating is safer than deciding.
Those are very different operating systems.
16
A leader who answers every difficult question eventually becomes part of the workflow.
That can look like leadership.
It is also how dependency gets institutionalized.
The test is not whether people can execute without you.
Can they exercise judgment without you?
15
A useful stress test:
Remove one of the three people carrying the most judgment and coordination.
Now change something important.
What breaks next tells you more about organizational capability than the utilization report.
10