# Beth McHugh

Beth McHugh works with EdTech teams on product strategy and Jobs to Be Done research, helping them understand what drives customer decisions and make better-informed product choices.

- Profile: https://b2binfluencer.marketing/creators/beth-mchugh/
- LinkedIn: https://www.linkedin.com/in/beth-mchugh-jtbd
- LinkedIn followers: 3,394
- Topics: product-management, customer-research
- Based on 19 dated posts, latest 2026-09-23

## Summary

Most useful for EdTech product strategy and Jobs to Be Done research that explains customer decisions.

- Best for: EdTech venture capital firms and product teams needing advisory or diligence support.
- Not for: Paid sponsorship, co-marketing, broad consumer campaigns, or fast feature shipping as progress.
- Check first: Ask for rates, available formats, and a recent audience breakdown before planning.

### Takeaways

- Plans are tools; the people closest to the work hold the judgment.
- Customer research should explain a decision, not collect complaints.
- AI can speed prototyping, but it cannot create shared customer understanding.

## Main ideas

- **Plans are tools; the people closest to the work hold the judgment**: McHugh argues that detailed plans—curricula for teachers, roadmaps for product teams—are treated as if they can anticipate realities beyond anyone’s control. When reality diverges, leaders typically rewrite the plan, add process or blame execution. The plan should be a tool, they say; expertise should sit with the people doing the work. High-quality decisions require experienced people who are compensated accordingly, or earlier-career talent whose judgment the organization actively develops.
- **Customer research should explain a decision, not collect complaints**: McHugh describes feeling overwhelmed by stakeholder feedback, opinions and a backlog, and says Jobs to Be Done gave them a way to focus. They talk to people who actually made a decision, ask about the events leading up to it, and listen for the forces pushing toward and against change. They distinguish annoying problems, which people readily name, from the demand problem that caused someone to switch. They repeat Bob Moesta’s line, “Bitching ain't switching,” to make the point that a complaint does not prove someone will act.
- **The hardest EdTech problems sit one level above the product**: McHugh argues that teams refine features while the surrounding system—states, districts, funding cycles, procurement, parents and teachers—shifts in ways a roadmap cannot track. Change the parts without changing the structure, they say, and the system snaps back. Without a clear hypothesis about how the system produces student outcomes, each shipped feature is a guess dressed up as progress. They favor mapping the whole system, finding leverage points and placing fewer bets that move everything else with them.
- **Mission and incentives drift apart, and the numbers quietly replace value**: McHugh describes EdTech companies that start with a mission and drift toward revenue or board-facing metrics. They argue that motivation slips when people sense a disconnect between the mission and what gets rewarded, and that usage, renewals and margins can become stand-ins for value without anyone showing the connection is real. They suggest balancing clear demand understanding, holistic measurement, governance, system understanding and funding streams that support the mission rather than compete with it.
- **AI can speed prototyping, but it cannot create shared customer understanding**: McHugh is skeptical of the idea that AI means designers should mainly judge PM-generated prototypes or maintain design systems. AI makes product ideas easier to visualize, they write, but it cannot fix a team where customer understanding sits with a small group: ideas get handed down and context gets lost. Strong product teams keep product, design and engineering close to discovery so anyone’s prototype can be challenged, improved and built on. They also warn against reducing Jobs to Be Done to a user story template and calling it JTBD.
- **Motivation follows progress toward something the learner cares about**: McHugh argues that students are motivated not by a subject or tool itself, but by the progress it helps them make toward something they care about. They worry that education’s focus on standards, test scores, pacing and curriculum can crowd out what makes students want to learn, and frame that as a Jobs to Be Done question: What progress is the student trying to make?

## Work to read

- [Why roadmaps and curricula fail when they try to predict messy reality](https://www.linkedin.com/posts/beth-mchugh-jtbd_there-is-a-pattern-i-keep-seeing-in-edtech-activity-7449515131597914112-HTB6)
- [What a request for unfounded financial projections reveals about mission drift](https://www.linkedin.com/posts/beth-mchugh-jtbd_im-reading-eric-ries-incorruptible-and-activity-7495929039505809408-9U3y)
- [Distinguishing annoying problems from demand problems when renewals stall](https://www.linkedin.com/posts/beth-mchugh-jtbd_jtbd-edtech-productmanagement-activity-7481009004287094785-7KOJ)
- [Why EdTech impact requires systems thinking, not more features](https://www.linkedin.com/posts/beth-mchugh-jtbd_systemsthinking-productstrategy-edtech-activity-7459662966406328320-VnKh)
- [How a flood of feedback led McHugh to Jobs to Be Done](https://www.linkedin.com/posts/beth-mchugh-jtbd_this-past-week-at-edtech-week-i-found-myself-activity-7387544448781492225-4qqj)
- [AI prototypes do not fix weak customer understanding](https://www.linkedin.com/posts/beth-mchugh-jtbd_product-collaboration-jtbd-activity-7470836119148933120-KuEB)

## Brand relationships

- **Supra** (disclosed_partnership)
- **EdTech Week** (mention)
- **Clayton Christensen Institute** (mention)
- **UPenn Center for Social Impact Strategy** (mention)
- **Volta** (mention)

## Partnerships

Beth McHugh's posts do not include a sponsorship offer, media kit, rate information, or partnership inquiry route. The posts describe their own research and advisory work rather than brand partnerships: Beth McHugh has written about being brought in as a fractional product leader (August 19, 2026), about coaching product managers through Supra (March 30, 2026), and about the client work they do helping EdTech teams understand demand (July 9, 2026). Nothing in the posts here identifies a sponsored format, a disclosure practice, or a way for a brand to commission content from them. A buyer should treat partnership availability as unverified and plan on direct outreach rather than a published process. Note the distinction: this describes an absence in the posts here, not a statement that they never accept sponsorships or paid collaborations.

## Alternatives

- Melissa Johnson: Choose Melissa Johnson when the advisory question is whether a K-12 sales organization's forecast can be trusted. Her two posts address a problem a venture firm might bring to diligence: a responsive buyer is not necessarily a committed one. Credibility comes from weekly pipeline inspection, a shared standard for buying signals, and coaching that surfaces who owns the decision, whether funding has been identified, and what happens if procurement slows the deal. She also describes building an AI-supported sales leadership process to pressure-test assumptions and prepare coaching questions across more opportunities. If the portfolio company's risk lies in revenue execution rather than product direction, she addresses it directly.
- Shannon Terry, Ed.D: Choose Shannon Terry when the diligence question concerns teacher evaluation, TIA-aligned incentive models, or implementation within district constraints. One post argues that buying a product does not guarantee transformation and that vendors must help districts navigate the operational realities of implementation. Another shows the rating-consistency problem in practice: two principals rate the same lesson differently, shifting compensation and designations as a result. Terry writes from inside that problem as president of the RefynED advisory board. For a portfolio company selling evaluation or educator-retention software, that perspective is closer to the buying question than general product strategy.
- Staci Lapis, M.Ed: Choose Staci Lapis when the question is about early product design craft and the practitioner's view of a student-facing product. Lapis was a teacher before moving into product design, and the description of the Studywavve app covers concrete decisions: onboarding that auto-populates a profile, filters for subject, language, and nearby peers, scheduling for virtual collaboration, and messaging for assignment feedback, aimed at students with limited access to materials. For a pre-seed or seed deal where the risk is whether a design-led product is genuinely usable and equitable, a former classroom teacher who builds the interface speaks to a different part of the decision than a strategist does.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/