Build The Thing Nobody Assigned You

50 YEARS, 50 LESSONS - BONUS LESSON

◆ Why "doing your job well" has a ceiling that "building the job that doesn't exist yet" doesn't

◆ The difference between scope creep that takes credit from other people and expansion that lifts the whole business

◆ The three guardrails that separate a smart bet from a reckless one: leadership air cover, protecting your actual numbers, and knowing when a hunch is enough versus when you need data

Most people treat their job description as the whole job. Hit the targets. Sometimes beat them. Get the good review. Get the promotion eventually. That's not a criticism, it's a completely rational way to operate, and it works. It's also capped, because a job description is a document someone wrote in the past to solve a problem the business had at the time.

The business doesn't stay still. The job description does. Every year that gap gets wider, and almost nobody walks into it. Your job description was written before the business needed what it needs now.

I didn't get hired to build a radio network or a podcast business. Out of Phone, TikTok Radio, the Podcast Network, none of that was in any job posting. It existed because the gap was obvious to me and invisible, or at least unclaimed, to everyone else with a reason to build it.

This pattern shows up everywhere once you know what you're looking for. Art Fry at 3M used the company's famous free-time policy to solve a problem nobody assigned him: bookmarks kept falling out of his church hymnal. He grabbed an adhesive one of his colleagues had already invented and shelved, and spent about eighteen months turning it into Post-it Notes, now one of 3M's biggest products ever.

Sony nearly walked away from gaming entirely after a partnership with Nintendo fell apart. Ken Kutaragi kept building anyway, developing 3D graphics technology the company had told him to drop. He kept at it quietly until he finally showed leadership what his team had built without anyone signing off on it. The response was two words: do it. That's the PlayStation business.

Paul Buchheit built Gmail because his own inbox was miserable to use. He shared an early version inside Google, and people started asking for access before it was ever a real product. Same instinct built Slack: the founding team was trying to make a video game that failed, and the internal messaging tool they threw together just to talk to each other quietly became the actual company.

None of them waited for a project charter. They noticed something, started building before anyone assigned it to them, and only got permission after the evidence was already sitting in front of leadership. That's the reverse of how most of us are trained to operate: get permission, get budget, staff the team, then start. Flip that order and you get Post-it Notes, PlayStation, Gmail, and Slack instead of another initiative that dies in a planning deck.

Grace Hopper used to tell the people who worked for her that it's easier to ask forgiveness than it is to get permission. She meant it as encouragement to think independently, and it's the whole philosophy of this lesson in one sentence.

There's an important line here and I want to be precise about it, because this is not permission to go build an empire by absorbing everyone else's work. That's a different move, and it's a bad one. Empire building takes territory that already belongs to someone. It creates enemies and it creates a business that depends on your ego instead of your output.

What I'm talking about is the opposite. It's building in the white space next to what already exists, not on top of it. Nobody has to lose a mandate for you to gain one. You're not redrawing anyone's lane, you're paving a new one.

That distinction is the whole game. Ask yourself before you start: does this require taking something from a specific person, or does it require noticing something nobody's been asked to own? If it's the first, stop. If it's the second, you've found it.

None of this works if you're doing it alone against your own leadership. You need someone above you who at minimum tolerates it and ideally sponsors it. Going fully rogue isn't brave, it's just risk with worse odds. Find the person who'll give you the air cover to keep going, even if all they say is "don't blow up your day job." That sentence is worth more than it sounds like.

Which brings up the actual rule. Your scoped job gets funded first, every time. If the new thing is eating the hours that should be showing up as your actual numbers, you haven't found leverage, you've found a distraction with a better story attached. The people who pull this off protect their core output like it's non-negotiable, because it is.

And know how far you're swinging. Stay close to your existing business line and a hunch is usually enough to start, because the downside is small and the context is already yours. The further out you go, the more credibility you're spending on a guess, and the more you need to walk in with data instead of conviction. Close in, ask forgiveness. Far out, bring receipts.

Here's the part nobody tells you going in. The first six months of building something outside your scope, you get almost nothing for it. No credit, sometimes mild suspicion, occasionally a direct "why are you spending time on this instead of your actual job." There's no budget line for it and no OKR that recognizes it. You're doing it on top of the job you're already measured on.

That's exactly why so few people do it, and exactly why it compounds so hard for the ones who do. Nobody's competing with you in the white space because the white space doesn't look like opportunity yet. It looks like extra, unrewarded work. It only starts looking like opportunity in hindsight, after somebody's already built it.

If you want to try this, don't ask for permission to build the big version. Build the smallest possible proof that the adjacent thing is real. One pilot, one deck, one working example. Let the results ask the question for you instead of asking it yourself up front. Nobody says no to something that's already working.

Look at your own business this week. Find the one thing that's obviously missing, sits next to your actual role, and belongs to nobody. Don't pitch it. Build the smallest scrappy version of it you can.

Then tell me which one you are.

BUILDS if you take the risk and build beyond your scope. STAYS if you stay in your lane and deliver what's asked.

Dan Page

newsletter.therealdanpage.com