This is the second post for App Zero: Get Mobile Right the First Time is a series for PMs at established companies who've been handed a mobile mandate and don't want to blow it. Here’s the first post.
TL;DR
A mandate is not alignment. The clapping in that kickoff meeting doesn't mean everyone is moving the same direction. Engineering, design, and leadership all have different fears. You can't argue people out of fears they haven't admitted to.
Run a two-week discovery sprint with a signed, written output. Write an MVP definition leadership can actually picture. And when someone escalates for their pet feature, hand them the bill and ask them to sign it.
The C-suite announced the initiative. Everyone nodded. Someone said: “Customer-centric.” There was a slide with a rocket emoji. People agreed it’s needed.
Then the meeting ended.
A mandate is not alignment. It’s just permission to start the hard part. And the hard part is the people. Engineering doesn’t want a second codebase. Design has never thought in touch targets. Leadership has a vague picture in their head that looks like Instagram but costs nothing. Getting all three moving the same direction before you’ve written a single line of code is the actual job.
Most companies don’t fail at mobile because they picked the wrong features. They fail because they never actually got aligned in the first place. They just assumed the clapping meant something.
The Scope Fight Is Never About Scope
I’ve sat in a lot of mobile scoping meetings. They all go the same way. Engineering wants to cut. Stakeholders want to add. Design wants three more weeks. Nobody is actually listening to each other. An hour passes. Everyone leaves annoyed, and nothing is resolved.
What’s actually going on in that room has nothing to do with features. It’s fear.



