We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Big Ideas
Agents are forcing a better definition of engagement. Scott Belsky argues that a person who gets value from a service every day through an agent is a DAU even if they never open the digital product; the interface can change, while the goal is an indispensable underlying resource. Apply: make the core engagement metric reflect recurring value delivered—such as a job completed or a decision advanced—and retain interface visits as a separate diagnostic for UX health and distribution.
Future-proof positioning must still sell today. April Dunford frames positioning as how a product best delivers value for a clearly defined customer, not as a marketing label. In one example, repositioning a desktop spreadsheet/SQL tool as an embeddable mobile database changed the target market, sales model, pricing, roadmap, and synchronization requirements. For an AI transition, first align executives on differentiated value, then explain why it matters in the future and offer a staged adoption path: map processes; start with low-risk, human-checked work; automate after repeated success; add exception handling; and retain humans for the hardest cases. Avoid promising a distant autonomous future that gives customers a reason to wait. Recheck competitive alternatives, differentiated capabilities, value themes, and changes in customer buying behavior every six months, using advisory boards, executive account calls, or systematic sales feedback.
Use AI to remove recontextualization tax, not to flatten reality. The Beautiful Mess describes the cost of translating complex operational reality into simplified reports for powerful or time-poor audiences: companies either spend heavily on the translation or wing it at the last minute. With reasonably fresh raw context, AI can produce audience-specific views while teams continue working in their own tools. Preserve the underlying context and create deliberate translation layers for each stakeholder instead of forcing one roadmap format or abstracting the product around every client workflow.
Tactical Playbook
Validate an unfamiliar domain before writing software. A practical community sequence is:
- Cold-DM practitioners, offer to pay for roughly 20 minutes, and ask them to walk through one recent workflow; permit redacted screen sharing where useful.
- Ask what arrived late, which spreadsheet they reopened, what they copied between tools, and where something nearly got missed.
- After five conversations, choose one repeated headache and handle it manually for a practitioner before building the first version.
- Start with one ICP, about 50 verified contacts, and one concrete reason to reply; scale outreach only after the first conversations.
This converts a vague market thesis into observed behavior and a low-cost test. Established competitors and their one-star reviews become sharper interview prompts, not reasons to abandon discovery.
Case Studies & Lessons
Payelle simplified payment choice by moving into the wallet. The team started with a recurring problem: choosing among cards with different rewards at checkout. It shifted from a physical-card concept to mobile wallets, aiming to surface the right existing card at payment time rather than make users open a separate app, search for a merchant, inspect rewards, and return to checkout. Eighteen months later it had built the technology, filed IP, launched, and entered discussions with large companies and financial institutions—but still identified distribution as an unresolved risk. The lesson is to move into the moment where friction occurs before adding another destination, then treat distribution as a separate post-launch hypothesis.
Know when to stop shipping. Paul Graham reports telling a startup that its product was already good enough and that it should stop writing code to focus entirely on acquiring customers; the team listened. PMs can make this handoff explicit: once quality is acceptable for the target user, shift capacity to activation, sales, or retention experiments rather than polishing another feature.
Career Corner
For senior-PM interviews, slow down and compress the answer. Advice from the PM community is to breathe, identify what is actually being asked, clarify when useful, lead with the important point, let it land, and stop before rambling. A simple response structure is three beats: situation, call, what changed. Practice saying that structure once before the next interview loop; it makes judgment easier to hear than speed does.