Mission

At ten people nobody needs to write down what the company is for. Everyone sits in the same room, so who is doing what and why travels by conversation. At forty people that stops working. New hires see only the work their own team owns, and they fill in the direction of the company by guessing.

The same question then gets different answers. A candidate in an interview asks what the company does, and one person says it's a document tool, another says a team collaboration platform, another names a well-known competitor and says "like that." None of those is wrong, and the candidate has now heard about three companies.

The same thing happens when features get chosen. If there's nothing to appeal to when someone asks whether a piece of work is really ours to do, what's left is who argues hardest and whatever the last customer asked for. A growing company can do more things every quarter while its filter stays the same size, so the direction drifts toward whoever is requesting. A mission fixes that filter in one sentence.

A usable mission sentence carries three pieces: who it's for, what changes for them, and how far the scope runs.

1. The subject. A specific group rather than everyone. Write "all people" and no request ever falls outside the sentence, which costs you the only thing it was for. Pagedeck's subject is teams that write documents together.
2. The change. What becomes different for that group, stated as a verb. The trick is to describe what happens on their side rather than what happens on yours — "we build a collaborative document tool" is your activity, not their change.
3. The scope. The sentence should make it readable where your work ends and someone else's begins. Without this piece nothing gets filtered in a meeting, because every proposal can be argued to serve the subject somehow.

Put the three together and Pagedeck's mission reads: turn scattered documents into a team's shared memory. The subject is the team, the change is scattered becoming shared, and the scope is documents. When someone proposes a scheduling feature, there's something to hold it up against.

A few conditions apply to the form as well. One sentence, present tense, and specific enough that it stays true to you after the company name is removed. "We deliver the best value to our customers" works with any company name dropped into it, so it can't do the job. Leave measurable targets out too: a date or a number means rewriting the sentence once it passes, and this is the line that has to be true both today and next year.

It gets written by the founders, or by the chief executive. A workshop can gather input, but the person accountable for the company's direction settles the wording, and it isn't a thing to put to a vote. It's usually fixed early, alongside the core values that decide close calls, and left alone unless the business itself changes. A mission that gets rewritten every year can't function as a test.

Four groups read it, for four different reasons.

1. Employees use it as the test in everyday decisions. It gets cited most often when candidates are being cut in a strategic priority session, where a few focus areas get chosen for the period.
2. Candidates read it in job posts and interviews as material for judging the company. At equal pay, which sentence someone agrees with is often what decides.
3. Investors read it to see whether this is a one-feature business or one with a longer story behind it.
4. Customers rarely read the sentence at all, but they read it indirectly through what the product refuses to become, and through the requests that never get built.

Because one sentence serves four directions, a mission tuned to only one of them shows quickly. A version inflated for investors is unusable in a meeting, and a version narrow enough for internal work reads from outside as a feature description.

"I think that feature sits outside our mission."

Signalling that the objection rests on an agreed scope rather than on taste.

"Leave the mission alone and rewrite the vision and this year's priorities."

Diagnosing the direction as fine and the destination and current focus as out of date.

"Our mission is so broad that it never tells us what not to do."

Pointing out that the sentence passes every proposal, so the scope needs narrowing.

At Pagedeck the sentence earned its keep when someone proposed a scheduling feature. It was the most frequent request coming through sales, and Sofia counted two deals lost over it. Mia said the team could build it but couldn't see how it connected to turning documents into shared memory.

Grace put the mission on screen and split the proposal into two questions: is this tracking the action items written in a document, or is it managing the team's calendar? The first starts from a document and sits inside the scope; the second is a different product. They shipped action-item extraction from meeting notes and nothing else. The mission didn't supply the answer — it let one proposal be asked as two.

The most common mistake is treating the mission as external copy. It sits at the top of the careers page and on the first slide of the company deck, so it looks like marketing, and at plenty of companies that's all it is. But the sentence earns its value inside the building, at the moment something gets turned down. Hung up as decoration it becomes a line nobody quotes in a meeting, which leaves you with one more advertising slogan indistinguishable from a value proposition, the compressed reason a customer should pick your product.

Believing bigger is better is the other common one. "We make the world better" reads well and is impossible to argue with. The problem appears the moment you try to use it. A broad sentence passes every proposal that comes up, which makes it decorative by construction. There's a simple way to check whether a mission is working: count the proposals turned down on its authority in the last six months. If the answer is zero, the sentence is either too wide or nobody is reading it.