Inside the Company
Keyboard: ← → to move, F for full screen, O for overview.
A series · Ten posts
Inside the Company
Corporate or owner-run? A framework in ten posts.
Muhammet Şafak
Series · 1–5
Ten posts
- 01Corporate or Owner-Run?size isn't the divide
- 02How Decisions Get Madechain or one signature?
- 03Process: Armor or Shackle?
- 04Role Boundarieseveryone does everything
- 05How Knowledge Flowshallway or document?
Series · 6–10
Ten posts
- 01Performance, Promotion and Paythere's always a negotiation
- 02Meetings and Reportingvisibility theater
- 03A Crisiswhere character shows
- 04What Breaks as a Company Growsfrom owner-run to corporate
- 05Which Company Fits You?a phase, not an identity
01 · Corporate or Owner-Run?
It isn't size.
The type of company you work for determines how much of your work is really yours.
01 · Company type
Four axes that separate them
- Where are decisions made?Does a role decide, or a person?
- How much is written down?Not just code: is the reasoning behind decisions written?
- Who is the cost of a mistake charged to?When something blows up, is the first thing sought a cause, or a person?
- How long is the time horizon?Is the company thinking about this quarter, or three years?
Corporateness is the ability to separate a decision from a person. An owner-run company is one where the decision stays with the person.
02 · How decisions get made
One-way door, two-way door
| Criterion | One-way door (decide slowly) | Two-way door (decide fast) |
|---|---|---|
| Examples | Data model core, a contract, a hire | Library, folder structure, screen layout |
| Owner-run company's mistake | Twenty minutes: "we'll fix it later" | Usually behaves correctly |
| Corporate's mistake | Usually behaves correctly | Forms a committee, stalls three months |
02 · What an approval chain is really for
Split the decision from the person.
An approval chain doesn't prevent mistakes; it slows them down and spreads them around. The institution's memory should outlive the memory of whoever made the decision.
Process is spreading the cost of a past incident over the future, in instalments.
03 · Process
When do you add process?
- The same mistake a third timeOnce is coincidence, twice is bad luck, three times is a pattern.
- Critical work sits with one person"Only Ahmet knows how that works" isn't a joke, it's a risk report.
- The team has grownIn a team of five, process is unnecessary because coordination happens at the table anyway. At twenty-five, it doesn't.
03 · Agility or indifference?
Does the same mistake keep happening?
If not, that's real agility. If so, what you call "agile" is indifference.
A capable person gets pulled into every gap, and the reward is more gaps.
04 · Three lines of clarity
Three lines for every critical piece of work
- D
Decides
Who says "yes/no"?
- E
Executes
Whose calendar hours go into this work?
- I
Informed
Who must know, or the work blows up?
04 · Close the gap, make it visible
A verbal boundary isn't a boundary.
Close the gap; make it visible that you closed it. Without the second sentence, the first isn't a sacrifice, it's a cover-up.
05 · How knowledge flows
Not the decision. The reasoning.
What the person who arrives six months from now needs isn't your decision, it's your constraint.
05 · Five minutes
What to write, and where
- We chose X because constraint Y existed. (pending)
- We had ruled out Z because W. (pending)
- Anywhere works: a pull request description, a task comment, the team channel. (pending)
05 · The test
Why is it like this?
In a healthy place, the answer points to a document. In an unhealthy place, the answer points to a person.
Having a system didn't change the outcome; it only changed the language of the negotiation.
06 · Pay
Two desks, two languages
| Criterion | Corporate | Owner-run company |
|---|---|---|
| What a raise is made of | Band, rating and calibration | Last three months, loyalty, cash that day |
| What it produces | Defensibility | No system, so the narrative is everything |
| Its price | No exceptional reward for exceptional work | Proximity is leverage |
| Your job | Put good work in the system's language | Remind |
06 · The conclusion
Pay isn't a reward. It's a negotiation.
And the negotiation has already started, whether you've noticed or not.
07 · The author's observation
Two extremes, the same theater
- 11 hMeetings per weekNo decision was made in any of them
- 3×The same informationTold to different people in different rooms
- 4"What are you up to?" a dayNo meetings, endless interruptions
- 40 minA five-minute questionThey have to rebuild the structure in their head
07 · A practical distinction
Three kinds of meeting
| Kind | Purpose | What comes out? | Necessary? |
|---|---|---|---|
| Decision | Make a choice | A decision and its owner | Yes, short |
| Discovery | Understand the problem | A better question | Yes |
| Status | Report the state of things | A record | Often no |
07 · The test
A decision, or a record?
Is this meeting producing a decision, or just a record?
08 · A crisis
Fear stretches time to detection.
And time to detection is the real cost of a crisis.
08 · Reflexes
A culprit, or a procedure?
| Criterion | Owner-run company | Corporate |
|---|---|---|
| Reflex | Looks for who's at fault | Produces a procedure |
| Its logic | Decision in a person, so fault in a person | Decision in a role, so fault in the system |
| Its price | Speed breeds fear; fear kills reporting | The postmortem can turn into a performance |
08 · The healthy reflex
How was this possible?
The real test comes six weeks after the crisis: the measure isn't what was said, it's what has actually changed six weeks later.
09 · Not a law, a pattern I've seen
What breaks as a company grows
| Approximate threshold | What breaks | What you first hear |
|---|---|---|
~10 people | The owner can't see everyone anymore | "I wasn't aware." |
~30–40 people | Middle management is born | "There's someone responsible for that team, let me ask them." |
~100 people | Departmental silos | "They're our internal customer." |
09 · The same thing breaks on every row
Informal coordination.
What used to get solved in the corridor can no longer be solved in the corridor. Processes aren't the cause of that need, they're the consequence.
10 · Which Company Fits You?
No right type, only a wrong match.
A company type isn't an identity, it's a set of constraints.
10 · Eight questions for the interview · 1–4
What do you ask, what does it measure?
| Question | What it measures |
|---|---|
| 1. Who can reverse this decision? | Whether decisions live in a person or a role |
| 2. Is there a process you've removed in the past year? | Whether the process is alive or dead |
| 3. What was the first question asked in the last serious outage? | Fear or curiosity |
| 4. Who makes promotion decisions, and on what evidence? | Whether effort is measured |
10 · Eight questions for the interview · 5–8
What do you ask, what does it measure?
| Question | What it measures |
|---|---|
| 5. How often does the founder/owner get into the codebase? | Whether the handover has happened |
| 6. What unwritten rule exists here? | The honesty of the culture |
| 7. Why did the last three people leave? | Whether the company knows itself |
| 8. Who declares a piece of work "done"? | The clarity of boundaries |
Choosing knowingly beats enduring blindly.
The decision about where you are
Who can reverse this?
If the answer is you, everything else is detail.