👋 Hey friend,
It’s mid-December, and I’ve been thinking about how fast everything moves now.
Strategy that felt locked in September gets completely rewritten by November. Priorities that were “top of roadmap” last quarter aren’t even in the conversation anymore. Leadership asks for one thing on Monday and something completely different by Friday.
If you work in tech right now, you know this feeling.
The ground is always shifting. The pace is relentless. Every company is moving at lightning speed because if you’re not, someone else is.
And in all that chaos, it’s really easy to lose the plot.
The Antidote to Chaos
Here’s what I keep coming back to when everything feels like too much:
First principles thinking.
Not the fancy startup version where you reinvent physics. The simple version:
Just talk to customers.
Deliver value.
That’s it.
When I’m stuck on what to build next, I talk to customers.
When I need feedback on a new design, I talk to customers.
When I need to challenge a leadership call on strategy, I back it up by talking to customers and getting data.
It sounds almost too simple. But in a year where everything felt like it was changing every other week, customer conversations were the one constant that kept me grounded.
Want to get the most out of ChatGPT?
ChatGPT is a superpower if you know how to use it correctly.
Discover how HubSpot's guide to AI can elevate both your productivity and creativity to get more things done.
Learn to automate tasks, enhance decision-making, and foster innovation with the power of AI.
Why First Principles Matter More Now
The thing about moving fast is that you can build a lot of stuff that doesn’t actually matter.
You can ship features because a competitor launched something similar. You can prioritize requests because a big customer asked for it. You can chase metrics that look good in a slide deck but don’t move the needle for real people.
Speed without direction is just chaos.
First principles thinking cuts through all of that. It forces you to ask:
What problem are we actually solving?
Who are we solving it for?
How do we know this matters to them?
When strategy changes every quarter, when leadership pivots priorities, when you’re drowning in feature requests, those three questions become your anchor.
And the fastest way to answer them? Talk to customers.
💡 Quick Tip: If you can’t explain why you’re building something in terms of a real customer problem, you probably shouldn’t be building it yet.
The Pattern I Saw This Year
Looking back at 2025, here’s what I noticed:
The projects that landed well, the ones that got high CSAT, strong adoption, and actually moved our business metrics, were the ones where we spent the most time talking to customers upfront.
The projects that felt like a slog, were the ones where we were guessing, or building based on assumptions, or chasing a competitor feature without understanding if our customers actually cared.
One example: We almost prioritized a feature because leadership saw it in a competitor’s product. It looked impressive. It seemed like table stakes.
But when we talked to customers, they didn’t care about it. At all. What they actually wanted was less loading spinners.
If we hadn’t talked to them, we would’ve burned so much time building something that didn’t matter.
The Future of Shopping? AI + Actual Humans.
AI has changed how consumers shop, but people still drive decisions. Levanta’s research shows affiliate and creator content continues to influence conversions, plus it now shapes the product recommendations AI delivers. Affiliate marketing isn’t being replaced by AI, it’s being amplified.
My End-of-Year First Principles Toolkit
Here’s how I use first principles thinking when things get chaotic:
1. Default to customer conversations
When in doubt, schedule a call. Not a formal research session. Just a conversation with someone who uses your product.
Ask them what’s working, what’s frustrating, what they’re trying to accomplish. You’ll learn more in 30 minutes than you will in three strategy meetings.
📌 Try this today: Block 30 minutes on your calendar in first week back from the holidays. Title it “Customer call.” Then reach out to a handful of users and ask if they have time to chat about how they’re using your product.
2. Use “customer problem” as your decision filter
Every time a new request or idea comes up, ask: “What customer problem does this solve?”
If you can’t answer that clearly, it’s not ready to be prioritized.
If the answer is “leadership wants it” or “our competitor has it,” dig deeper. There might be a real customer problem underneath, but you need to find it first.
📌 Try this today: Look at your roadmap. Pick one item. Write down the customer problem it solves in one sentence. If you can’t, that’s your signal to talk to customers before you build it.
If you’re not a PM, look at the problems you see users bringing up, support tickets, roadblocks. What are those common problems that keep coming up over and over again? - share those with the product team and leadership.
3. Ground strategy debates in customer data
When strategy changes or leadership proposes a new direction, the best way to evaluate it is through customer evidence.
Not “I think customers want this.” Not “this feels right.” Real data from real conversations.
This year, I challenged a strategic priority by showing leadership that customers weren’t asking for the thing we were about to build. We redirected to something with clearer customer demand, and it performed way better.
📌 Try this today: Next time you’re in a strategy debate, ask “What did customers say when we asked them about this?” If no one’s asked, that’s your opening to go find out.
4. Measure value delivered, not just features shipped
It’s easy to get caught up in shipping. But shipping isn’t the same as delivering value.
At the end of every project, I ask: “Did this actually solve the problem we set out to solve?”
Sometimes the answer is yes. Sometimes it’s “sort of.” And sometimes it’s “we learned something, but we need to iterate.”
All of those are fine. The key is measuring against customer impact, not just output.
📌 Try this today: Pick a feature you shipped recently. Talk to a customer who’s using it. Ask them if it solved their problem. Their answer will tell you everything.
Quick Reads for Grounding Yourself
The Lean Startup by Eric Ries: The OG playbook for customer-led building
Continuous Discovery Habits by Teresa Torres: How to make customer conversations a regular practice
Lenny’s Podcast with April Dunford: Positioning and first principles thinking
The Real North Star
Here’s what I’m taking into 2026:
Strategy will keep changing. Priorities will keep shifting. The pace won’t slow down.
But if I stay close to customers, if I keep asking “what problem are we solving and for who,” if I measure success by value delivered instead of features shipped, I’ll be grounded no matter how fast things move.
Talk to customers. Deliver customer value.
Everything else is just noise.
See you next Friday (and happy holidays if I don’t catch you before then),
– Stef
💬 Want to talk product? I’m mentoring on ADPList! If you’re trying to figure out what to prioritize, how to stay customer-led, or just need to talk through your 2025 roadmap, you can book a free session with me right here.
If you like Stef the PM, here are a few other reads worth checking out:
→ The Byte – Fast, punchy tech and AI news
→ Innovate Disrupt or Die – Strategic insights on innovation and disruption
→ Marketing Alec – AI-powered marketing strategies
→ Practical Marketing – No-BS marketing tactics that work
→ Two Dads in Tech – Honest conversations about tech careers and life
→ Cooking Agile – Agile practices made practical
→ Seedradar AI – Startup and AI trends to watch



