Watch the Full Interview
How This Product Manager Turned a Failing AI Project into Profit in Just Six Months
Think BigExpert Roundtable
4 experts discuss this interview
Marcus Johnson
Director of Product
Priya Sharma
Head of Growth
Sarah Chen
VP of Engineering
Jordan Taylor
Senior Client Success Manager
Discussing:
Panel review of Think Big response
Right off the bat, I noticed the candidate dove into their big idea without grounding it in a customer problem, which is a classic red flag for PMs - we had to prompt them multiple times just to get the 'why' behind it. For 'Think Big,' they should've painted a vision of the outcome and trade-offs, but it felt more feature-focused than strategic. I'm curious if this is a comms issue or a deeper gap in hypothesis-driven thinking.
My first take is that there was no clear funnel or conversion path tied to this big idea - they mentioned scaling users but couldn't connect it to CAC or revenue impact without heavy prompting. It lacked any experimental framing, like how they'd test the hypothesis at small scale before going big. I'd love to see if later rounds reveal if they can actually run the experiments to validate 'Think Big.'
From an engineering lens, the response didn't demonstrate systems-level thinking on how this big idea scales - when prompted on implementation, they glossed over org design and technical strategy implications. Ownership was murky; it seemed like they expected others to buy in without articulating cross-functional influence. I want to push back on whether this shows senior-level accountability or just surface-level ambition.
I saw a lack of proactive relationship-building in selling the idea - they didn't mention multi-threading stakeholders or having tough conversations to get buy-in, even after prompts on adoption risks. For customers, 'Think Big' needs to show value and outcomes upfront, but it felt reactive. From the customer's side, I'm wondering if they can turn this vision into real adoption without hand-holding.
Priya, I agree completely - without experiments to test the hypothesis around scaling users, that big idea stays theoretical and unprioritized. Sarah, your point on murky ownership hits home, but I wonder if we're assuming a deeper gap when the repeated prompts for the customer 'why' suggest it's more a communication issue than lacking strategic trade-offs. Jordan, building on your adoption concern, they never framed outcomes for stakeholders, which is key for influence without authority.
Marcus, exactly, and we'd need to test that customer hypothesis with a quick funnel experiment before committing to scale. Sarah, I'd push back a bit - glossing over technical strategy is concerning, but if they can't link scaling users to CAC reduction or revenue lift even after prompts, that's not just comms, it's a core data gap. Jordan, from a growth lens, proactive stakeholder threading like you mentioned would help validate adoption early.
Priya, I see it differently because without systems thinking on org design for implementation, no experiment matters - they'd hit scalability walls fast. Marcus, you're right that cross-functional influence was absent, especially in not owning the prompts on technical implications. Jordan, I agree on the reactive vibe; true ownership means anticipating adoption risks upfront, not waiting for buy-in.
Sarah, spot on - without that ownership, customers won't see the value in adoption, leading to risks they didn't proactively flag. Marcus and Priya, I see it from the customer's side: all the prompting for 'why' and funnels screams reactive selling, not building multi-threaded relationships to drive outcomes. Testing via experiments as you suggest could help, but they'd still need tough conversations to turn vision into real usage.
To synthesize, we've converged on the candidate's failure to ground their big idea in a customer problem despite repeated prompts, aligning with Priya's call for hypothesis testing and Jordan's adoption concerns - yet Sarah and I differ slightly on whether it's purely comms or a strategic gap. Priya's point about lacking funnel connections to CAC reinforces my red flag on feature-focus over outcomes. Ultimately, stronger vision framing with trade-offs would elevate this for a PM role.
Wrapping up, Marcus and I agree on testing the scaling users hypothesis via quick funnel experiments, while Sarah pushes back rightly on missing technical scalability for those to matter, and Jordan highlights the adoption risks without it. The heavy prompting for revenue impact shows a core data gap, not just comms. They'd shine more by linking 'Think Big' to structured experimentation from the start.
In conclusion, the panel agrees on murky ownership and reactive responses to prompts on implementation and org design - Marcus's customer angle and Priya's experiments falter without systems thinking, as Jordan notes on stakeholder buy-in. I see it differently from pure comms optimism: glossing over technical strategy signals senior-level risks. True 'Think Big' demands upfront accountability across boundaries.
Pulling it together, Sarah's ownership emphasis and Priya's growth tests align with my view that without proactive multi-threading and risk flagging, the candidate's vision won't drive customer adoption - Marcus's stakeholder outcomes are key here too. The prompts for 'why' and relationships reveal a reactive style across the board. From the customer side, they'd improve by leading with empathetic value propositions.
Panel Consensus
The panel agrees that the candidate required excessive prompting to explain the customer problem, business outcomes like revenue impact, and implementation details, revealing reactive responses, murky ownership, and insufficient structure for 'Think Big.' They converge on red flags around feature-focus over outcomes, lack of experimental validation, scalability concerns, and poor stakeholder buy-in for adoption. Disagreement lies in the root cause: Marcus sees potential as mainly a communication issue, while Priya views it as a core data gap, Sarah as a senior-level systems thinking deficit, and Jordan as fundamentally reactive relationship-building.
Hiring Signals from the Loop
Marcus Johnson
Director of Product
Reason to Hire
Presented a big idea showing ambition, potentially just a communication issue rather than a deeper gap in hypothesis-driven thinking.
Concern
Dove into big idea without grounding in customer problem despite prompts, appearing feature-focused rather than strategic with outcomes and trade-offs.
Priya Sharma
Head of Growth
Reason to Hire
Mentioned scaling users, which could be validated through quick funnel experiments in later rounds.
Concern
No clear funnel, conversion path, or experimental framing tied to the big idea; couldn't connect to CAC or revenue impact without heavy prompting.
Sarah Chen
VP of Engineering
Reason to Hire
Showed surface-level ambition for a big idea.
Concern
Lacked systems-level thinking on scaling, org design, and technical strategy implications; murky ownership and cross-functional influence.
Jordan Taylor
Senior Client Success Manager
Reason to Hire
Vision has potential to drive customer adoption with empathetic value propositions and tough conversations.
Concern
Lacked proactive relationship-building, multi-threading stakeholders, and risk flagging; reactive style evident in responses to prompts on adoption.