Strategy
Concept
The field that decides what a company earns money from, who gets to make that call, and how the call is checked afterward.
Why it exists
In a company of five, management never needs a name. The two founders sit at the same desk, so what to build, what to charge, and who to hire next all get settled over lunch and acted on that afternoon. Nothing sits between the decision and the work, so there is no reason to invent a process.
Past forty people the arrangement quietly falls apart. Most of the company was not in the room when the decision got made, and each team moves on its own best guess about where things are headed. When the guesses drift slightly apart, every team ends up building a different company.
At Pagedeck the failure looked like this. Marketing was running ads aimed at individual users. Sales was closing annual contracts with companies. Engineering took requests from both sides and alternated weeks, shipping a feature for individuals and then a feature for companies. All three worked hard, all three hit the targets they had been given, and at the end of the quarter neither the individual side nor the company side had taken hold, with two quarters of payroll gone. When someone in the quarterly review asked whether Pagedeck was a product a person uses or a product a company buys, nobody in the room could answer.
This field exists to settle in advance who answers that question, when, and on what evidence. The answer does not have to be right. If it is written in one place and everyone is reading the same copy, then when it turns out to be wrong there is exactly one thing to change. With no written answer, nobody notices it was wrong at all, and the company runs as many answers as it has teams.
How this field breaks down
The questions this field answers fall into four groups: who decides, what the company earns money from, when decisions get made and reviewed, and how the company handles the outside world and the future. Nine branches divide across those four.
Roles sort the field by who makes a decision. What separates the seats is not seniority but the scope of the decisions each one carries and how reversible those decisions are.
- Chief Executive Officer (CEO) — represents the whole company and makes the final call. Decisions that are hard to undo reach this seat: shutting down a market, or putting a particular person in an executive role.
- Chief Operating Officer (COO) — makes the agreed direction actually run. Work that falls between departments, hiring pace, progress against quarterly targets, anything that needs a hand every week. Plenty of companies leave this seat empty until they pass a hundred people and let the CEO carry it.
- Founder — the person who started the company. Someone who joined at the very beginning to build it alongside them is called a co-founder. The word describes history rather than a job, so no authority comes attached to it. Some companies have a founder who is not the CEO, and plenty have a CEO who never founded anything.
- Board of directors — the body outside the executive team that oversees and approves major decisions. Investors, founders, and outside members sit on it together. An advisor is the other kind of outside eye, someone who gives counsel with no authority behind it, while the board can approve a decision or block it.
Governance ties those seats into one set of rules. Governance writes down ahead of time which decisions end with the CEO, which need board approval, and what shareholders have a right to see. Pagedeck put any single expense above 50,000 dollars, any new fundraise, and any executive hire on the board agenda, and left everything else with Grace. The lines get drawn in advance because working out who to ask case by case delays every urgent decision by days.
Business structure covers where the money comes from. A business model bundles who gets what value and how they pay for it into one structure. Two document editors can be entirely different companies: one charges per person per month, one charges by storage used, one runs ads and charges nothing at all. Change how the money arrives and you change which number has to grow, and the number that has to grow decides which features get built.
Strategy is choosing what to do and what to skip inside that structure. Corporate strategy is the set of choices about which customers to serve and which strength to win with. Most of the content sits on the discard side. When Pagedeck decides to go after company accounts this year, that sentence also says nobody gets staffed on the individual plan. A document that gives nothing up is a wish list rather than a strategy.
Growth stage sorts by where the company currently stands. Startup stage names the segments a company passes through as it grows, and each segment has a different problem to solve. At ten people the homework is confirming that anyone will buy at all. At forty-five it is making the way you sell hold up when you add people to it. The same advice being right in one place and wrong in another comes from this. Hiring ten salespeople before anyone has renewed once is the standard version of getting the stage wrong.
Operations sets when decisions get made and when they get looked at again. A planning cycle splits time into periods, hands out goals, people, and money for each one, and checks the result when the period closes. Pagedeck runs on quarters. Two weeks before a quarter starts the team decides what the quarter holds, and the week after it ends they check whether that happened. Without a fixed cycle, setting goals still happens; going back to look at them rarely does.
Partnerships pull in strength from outside the company. A partnership is a relationship with another company that produces a result neither one reaches alone. Pagedeck attached video calls in two months by connecting to a company that does nothing else, where building the same thing in-house would have taken a year. The cost is that if that company raises its price or cuts the connection, one of Pagedeck's features wobbles with it. What to build and what to borrow is a choice this field returns to constantly.
Innovation prepares for the day the current way of earning stops working. Innovation management covers how new businesses and technologies get grown inside an organization. The hard part is that a new attempt gets weighed on the same scale as work that pays now. Put a feature worth 30,000 dollars this quarter next to an experiment that may or may not work two years out, and the first one wins every time. Three years of that leaves the company with nothing new to sell. The usual answer is to fence off budget and headcount so the two never compete directly.
Risk handles what could shake the company before it does. Risk management lists the accidents that could plausibly happen, weighs each one's likelihood against its size, and picks what to address first. A leak of customer data is unlikely but large enough to close the company, so it sits near the top. An outage that blocks access for two hours happens often and recovers, so it sits lower. Next to the top item Pagedeck wrote the response as well: who calls the affected customers, who cuts off the accounts involved, and who speaks for the company. The day an accident happens is the worst possible day to start inventing that plan.
The nine branches do not run separately. The business model has to be settled before strategy has anything to choose between. Strategy has to be settled before the planning cycle has anything to put in a quarter. The cycle has to run before growth stage can tell you how far along the company actually is. Along the way, the gaps the company cannot cover alone get filled by partnerships, the parts that will go stale get covered by innovation, and the parts that can go wrong get held down by risk management. Who decides all of it is roles. Who checks those decisions is governance.
How it sounds at work
"That isn't the CEO's call to make, it's a board item."
The decision crosses a line drawn in advance, so it has to go through approval.
"We're not doing the individual plan this quarter. Everything goes to the company side."
A sentence about what gets dropped from the list of things worth doing, which is what strategy is. The half that carries weight is the half naming what stops, because that is the half a team can point at when an urgent request shows up in week three.
"A Series A company is working like a Series C company."
Process and structure got built before the stage called for them, and speed went with it. Four approval steps on a decision two people could have settled in a hallway is the usual shape of the complaint.
Grace opens every quarterly planning session at Pagedeck with the same question: where is the company trying to win this quarter. Last quarter the answer was company accounts, so Sofia took a target of twenty signed contracts and Mia moved permission controls, the feature companies keep asking for, to the front of the build order. The campaign Ravi had been preparing for individual users had its budget cut in half.
The side that shrank did not lose an argument; an order got set. When the quarter closes Grace checks how many contracts came in and whether permission controls actually pulled them, then sets the answer for the next quarter. Sometimes it holds and sometimes it changes, and either way everyone walks out of the room carrying the same sentence.
What people get wrong
The most common mistake is treating this field as something only the CEO and the executives do. Its vocabulary shows up in rooms most people never sit in, like board meetings and investment negotiations, so the reading is understandable. But these decisions rewrite an ordinary working day. When the company commits to company accounts, the designer draws different screens, the engineer builds different features next month, and the marketer works from a different budget. Treating the decision as somebody else's business means never knowing why the work suddenly flipped, and every flip reads as management changing its mind. Far more often nothing flipped: the answer was written down and nobody read it.
The second mistake is reading strategy as a list of things worth doing. A quarterly plan with twelve lines on it, each one plausible, looks like a strong plan. But with a fixed number of people and weeks, committing to all twelve is the same as committing to half of each. A real strategy carries the list of what will not be done, and that second list is what lets a team refuse something when an urgent request arrives mid-quarter. A plan with nothing given up gets shoved aside by the first large customer request of the quarter, and the quarter ends with not one item finished. The next planning session then opens by copying the same twelve lines forward, which is how a team spends a year busy and arrives nowhere.
Where to go next
- Chief Executive Officer
the fastest way in, since it shows which desk these decisions end on
- Chief Operating Officer
the neighboring seat that keeps the direction running week to week, so the line between deciding and executing sharpens
Sub-terms
Last updated 2026-09-16