Watch the Full Interview
Why This Sr. UX Researcher’s Radical Approach to Policy Development Became a Game-Changer
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
My first take is that the candidate stayed too focused on internal process cleanup - like standardizing research templates - rather than starting with a bold customer problem or outcome we could rally around. They didn't frame it as a hypothesis to test against user needs, which makes me wonder if they can drive big strategic shifts. I'd love to hear if others saw more vision emerging as they got pressed for details.
I noticed they described an evolutionary tweak to their research workflow, improving efficiency incrementally, but without tying it to funnel impacts or revenue outcomes - it felt high-level without the data to back it. They only shared quant support after probing, like mentioning a 20% time savings, but no experimentation mindset to scale that thinking big. Curious if this hints at quick wins or just maintenance mode.
From a systems perspective, the candidate's example of cleaning up bad processes was more tactical fix than a scalable rearchitecture of research operations, lacking ownership for broader org impact. They improved when pushed on metrics, but started too abstract without quantifying how it enabled bigger technical or cross-team initiatives. I want to push back - does this show potential for senior-level thinking big, or just mid-level execution?
I see it from the customer's side: the candidate talked about proactive process fixes to deliver better research insights, which is good for adoption, but it wasn't framed as a revolutionary way to uncover risks or drive value at scale. They had to be prompted for specifics on outcomes, like faster user feedback loops building trust. Building on that, did anyone spot proactive relationship-building in their big-picture approach?
Priya, I completely agree that tying the 20% time savings to funnel impacts or experiments would have shown bigger thinking, rather than just workflow tweaks. Sarah, your pushback on it being tactical versus scalable resonates, especially since they didn't frame standardization of research templates as a customer hypothesis. Jordan, I wonder if we're assuming too much on customer trust from faster feedback loops without hearing how it drove outcomes or trade-offs.
Marcus, exactly, and we could've tested that customer hypothesis with quick experiments on research output quality to see conversion lifts. Sarah, I'd want to test your assumption about rearchitecture by running pilots on cross-team research scalability post-cleanup. Jordan, from a growth lens, proactive adoption sounds good, but without CAC reductions or funnel metrics from those insights, it stays evolutionary.
Marcus and Priya, that's right, and from an org design perspective, the 20% savings needed to quantify enablement of larger initiatives like multi-team research systems. I see it differently from Jordan - even proactive fixes for insights don't scale to Think Big without ownership of broader technical strategy impacts. Priya, experiments are great, but if they're not addressing systemic bottlenecks, they remain quick wins, not revolutionary.
Sarah, building on your org impact point, faster feedback loops could proactively identify adoption risks if framed with customer relationships in mind. Priya, I see it from the customer's side - the multi-threaded trust in research insights was implied but not bold enough without outcome stories like reduced churn. Marcus, exactly, and adding customer context, they needed to show how process cleanup unlocked value at scale through genuine stakeholder buy-in.
Wrapping this up, we all agree the candidate's focus on standardizing research templates and the 20% time savings was solid execution but stayed evolutionary, not the bold customer hypothesis needed for Think Big. Priya and Sarah, your points on missing funnel experiments and scalable org impact highlight why it felt tactical, while Jordan, I see your customer trust angle but we needed trade-offs shown. Overall, it raises questions on driving strategic shifts without starting from user outcomes.
Marcus, exactly, and without tying that 20% savings to conversion lifts or CAC reductions, it missed the experimentation to scale big. Sarah, your push on systemic bottlenecks aligns perfectly - no pilots post-cleanup meant no proof of revolutionary growth. Jordan, customer adoption is key, but high-level insights without metrics keep it in maintenance mode; this showed incremental wins, not bold funnel reimagination.
To synthesize, Priya and Marcus are spot on - the lack of quantified org enablement from process cleanup, like multi-team research systems, kept it from systems-level Think Big. Jordan, I push back gently: faster feedback loops imply relationships but without ownership of technical strategy impacts, it's not senior-scale. Final thought: improvement under pressure shows potential, but starting abstract signals mid-level tactical focus over revolutionary architecture.
Sarah, building on your org impact, we agree proactive fixes like quicker insights build trust, but all of us noted it wasn't framed boldly enough for scaled value or risk mitigation. Marcus and Priya, exactly - adding customer relationships to those metrics would have unlocked the big-picture outcomes. In conclusion, the response showed empathy in process fixes but needed multi-threaded stories of stakeholder buy-in to truly demonstrate Think Big.
Panel Consensus
The panel unanimously agrees that the candidate's focus on standardizing research templates for 20% time savings showed solid tactical execution and improvement under pressure, but fell short of 'Think Big' by remaining evolutionary rather than bold or revolutionary, lacking initial data, customer hypotheses, funnel experiments, and scalable org impacts. Minor disagreements emerge on nuances: Jordan emphasizes potential customer trust and adoption from faster insights, while Sarah pushes for stronger systems-level ownership, and Priya/Marcus stress missing experimentation and outcome ties. Consensus leans toward concerns about senior-level strategic vision dominating any positives.
Hiring Signals from the Loop
Marcus Johnson
Director of Product
Reason to Hire
Solid execution on standardizing research templates achieving 20% time savings, with vision emerging when pressed for details
Concern
Stayed focused on internal process cleanup without framing as a bold customer hypothesis or driving strategic shifts with outcomes and trade-offs
Priya Sharma
Head of Growth
Reason to Hire
Described incremental efficiency improvements like 20% time savings that could support quick wins
Concern
Lacked experimentation mindset to tie workflow tweaks to funnel impacts, revenue outcomes, or CAC reductions, remaining high-level without initial data
Sarah Chen
VP of Engineering
Reason to Hire
Improved under pressure with metrics, showing potential for senior-level thinking
Concern
Presented tactical process fixes rather than scalable rearchitecture, lacking quantified org enablement for broader cross-team initiatives or systemic impact
Jordan Taylor
Senior Client Success Manager
Reason to Hire
Proactive process fixes to deliver better research insights and faster feedback loops, supporting customer trust and adoption
Concern
Not framed as revolutionary for scaled value or risk mitigation, lacking bold outcome stories and multi-threaded stakeholder buy-in, requiring prompts for specifics