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.
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.
Key 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.
Check first: Ask for rates, available formats, and a recent audience breakdown before planning.
Main ideas
Plans are tools; the people closest to the work hold the judgment · Customer research should explain a decision, not collect complaints · The hardest EdTech problems sit one level above the product
Beth McHugh works with EdTech teams on product strategy and Jobs to Be Done research.
Their posts examine what drives customer decisions—and why roadmaps, adoption metrics, or mission statements can give a misleading picture of progress.
They cover practical problems such as stalled district renewals, teams planning for classroom realities they cannot predict, and products that make teachers’ work harder.
Their work helps readers understand customer demand and the wider systems that shape whether an education product gets used and helps students.
McHugh connects customer research to the conditions around a product.
In one post, they describe a product leader whose district renewals have slowed.
Rather than accept familiar explanations such as pricing or seasonality, they argue for investigating what changed in the decisions behind the purchases.
In another, they compare rigid roadmaps with curricula that cannot anticipate every classroom’s needs, making the case for giving people close to the work room to adapt.
They also look beyond the product to systems such as procurement, funding, and school operations, and warn that AI-generated prototypes cannot replace shared customer understanding.
By examining decision-making, on-the-ground experience, and the surrounding system, their writing helps readers distinguish visible activity from meaningful progress in EdTech.
Beth McHugh’s posts return to a few connected arguments: plans should support judgment rather than replace it, customer research should explain why people acted rather than collect complaints, and the hardest EdTech problems sit in the system around a product rather than inside it.
Read more
They treat Jobs to Be Done as a working method, not a template, and are candid about the gap between mission language and the incentives that decide what gets funded. Their recent writing adds a systems lens and a skeptical view of AI prototyping without shared customer understanding.
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.
Read more
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.
In a post about a pattern they keep seeing in EdTech, Beth McHugh compares classrooms where students arrive with different starting points, inconsistent support at home and limited time with product teams whose users behave differently once a product enters a real workflow. Rigid plans create a feeling of control, they write, but produce better-looking plans and worse outcomes.
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.
Read more
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.
In a post about stalled renewals, McHugh recounts a conversation with an EdTech product leader whose districts had stopped renewing without much thought.
Leadership already had answers—pricing, seasonality, a competitor.
Seasonality is real in EdTech, they note, which makes it a dangerous explanation: plausible enough that nobody looks closer.
Direct customer conversations, they argue, usually surface friction rather than the underlying shift in demand.
They first went deep on ODI, then connected with Aaron Young and Alec Latimer, whose focus on Bob Moesta’s approach challenged their assumptions and eventually led to meeting Moesta in person. McHugh says the exchange changed how they think about the work.
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.
Read more
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.
In a post on systems thinking, McHugh cites Donella Meadows’s Thinking in Systems, which they picked up after reading Bobby Moesta’s Learning to Build, and a talk by Dr.
Meghan Bausone that sent them back to Meadows.
In a separate post, they reflect on Halle Tecco’s book Massively Better Healthcare, arguing that healthcare and education face the same problem: strong innovations stay at the margins because interconnected incentives, funding structures and procurement models hold the system in place.
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.
Read more
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.
In a post about reading Eric Ries’s Incorruptible, McHugh describes being brought in as a fractional product leader and asked to build financial projections for a solution that had not been defined.
The numbers had no basis, but the board needed a funding story.
They pushed back; people agreed with them, but the numbers were still needed.
They connect that experience to a district that adopts a product for consistency across schools while teachers experience less autonomy and more work: the renewal looks good in a board deck, but the classroom tells a different story.
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.
Read more
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.
In a post on AI and product collaboration, McHugh describes the best product cultures they have worked in as improvisational: a designer pushes the experience further, an engineer finds a better technical path, a product manager connects it back to the customer struggle, and someone asks the question that changes the direction entirely. AI, they argue, can make the broken version of that process faster, not better.
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.
Read more
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?
In a post about their sons, McHugh describes them building a Father’s Day scavenger hunt with homemade currency, hidden paper money and a list of rewards—work they did during reading time and before the rest of the family woke up.
The same child who groans about a school project and fights with his brother over ordinary tasks showed up with effort in abundance.
McHugh uses the story to argue that no amount of explaining why something matters creates the energy of an idea someone actually cares about.
This post is the clearest single statement of McHugh's product philosophy: plans are useful only when they leave room for the people doing the work to adapt.
Read more
A newcomer should start here to understand why they treat rigid roadmaps and under-supported teams as a system problem, not an execution failure.
Beth McHugh describes a pattern they see in both EdTech and product work: detailed plans, whether curricula or roadmaps, are expected to anticipate realities they cannot control.
Teachers face students with different starting points, uneven home support, and limited time; product teams face user behavior that diverges once a product reaches real workflows.
When reality does not match the plan, leadership often rewrites it, adds process, or blames execution.
McHugh argues the artifact should be a tool, while judgment and expertise should sit with the people closest to the work.
For brands planning a campaign
For a strategic advisory role, this frames McHugh's value as helping leadership teams diagnose whether planning artifacts are masking deeper incentives and trust problems. A venture capital firm could use it to assess how a portfolio company responds when its roadmap meets real user behavior.
This original explains why McHugh cares about mission and measurement together, and why they use Jobs to Be Done as a practical lens rather than a slogan.
Read more
It gives a newcomer a concrete story about the kind of gap they want leaders to examine.
McHugh describes being brought in as a fractional product leader and asked to build financial projections for a solution that had not been defined.
The numbers had nothing behind them, but the board needed a funding story.
They pushed back, people agreed, and the numbers were still needed.
McHugh uses Eric Ries's Incorruptible to name the disconnect between mission and the incentives shaping decisions.
They then explain why Jobs to Be Done matters: a district may adopt a product for consistency across schools, while teachers experience less autonomy and more work.
The renewal looks good in a board deck, but the teacher and student experience tells a different story.
For brands planning a campaign
For advisory work, this supports a positioning around helping leaders examine the distance between mission language and the incentives that decide what gets funded. For a venture capital firm, it is a useful diligence prompt: are portfolio metrics standing in for value without showing the connection?
This post shows how McHugh turns a vague retention worry into a research problem.
Read more
Open it to see their method for separating comfortable explanations from the demand shifts that actually change buying behavior.
McHugh recounts a conversation with an EdTech product leader whose districts are no longer renewing without much thought and whose deals are stalling.
Leadership already has answers: pricing, seasonality, a competitor.
McHugh notes that seasonality is real in EdTech, which is exactly what makes it dangerous as an answer.
It is plausible enough that nobody looks closer, and the roadmap was set months ago.
The product leader lacks proof, only a pattern they cannot yet explain.
McHugh explains that asking customers directly usually surfaces annoying problems, the friction people can easily name, not the demand problem that caused them to switch.
The demand problem is buried underneath the easy answer and requires a different lens on interviews.
For brands planning a campaign
An advisory engagement could be scoped as a diagnostic sprint when retention metrics and leadership explanations diverge. A venture capital firm could use this lens to evaluate whether a portfolio company is defending a plan or investigating a real demand change.
This is the framework behind McHugh's recommendations.
Read more
It explains why they are skeptical of feature-level fixes and look at the wider system a product sits inside, which matters for anyone assessing their strategic advisory approach.
McHugh describes the feeling that no matter how much effort went into a roadmap and strategy, student outcomes were hard to move.
They cite Donella Meadows's Thinking in Systems, which they picked up after reading Bobby Moesta's Learning to Build, and a talk by Dr.
Meghan Bausone that sent them back to Meadows.
The key idea: a system's behavior cannot be understood by studying its parts in isolation.
Structure, how pieces connect and reinforce each other, produces outcomes.
In EdTech, the system includes states, districts, funding cycles, procurement, parents, and teachers.
McHugh argues the hardest problems live one level up from the product, and teams that break out will be the ones that see the whole system and find leverage points.
For brands planning a campaign
For a venture capital firm, this supplies a systems-level diligence framework: whether a company is optimizing a product while treating the surrounding structure as fixed. For advisory work, it supports engagements focused on mapping the system and placing fewer, higher-leverage bets.
This is the most direct account of how McHugh came to Jobs to Be Done and what they actually do with it.
Read more
A newcomer should open it to understand their core diagnostic questions and public teaching style.
McHugh describes speaking at EDTECH WEEK, something they say would have felt out of character years earlier.
They started as a computer science major, moved into UX and then product management, and eventually felt overwhelmed by feedback, stakeholder opinions, and a backlog that was impossible to prioritize.
They say they turned to Jobs to Be Done for clarity.
Their practice focuses on talking to people who made a decision, asking about the moments and events leading up to change, and listening for the forces pushing toward and against that decision.
McHugh repeats Bobby Moesta's line, Bitching ain't switching: complaints do not prove someone will act.
For brands planning a campaign
If an advisory role includes workshops or events, this post shows the questions McHugh would bring and how they frame JTBD for product teams. It is also a useful sample for a venture capital firm assessing whether their method can align a portfolio company around real customer decisions.
This original shows McHugh's view on AI adoption, collaboration, and research foundations.
Read more
It helps readers see why they would advise teams to invest in customer understanding before accelerating prototype production.
McHugh, who has a UX design background and now works as a product manager, says AI makes it easier to visualize product ideas but is skeptical that designers should shift mainly into judging AI output.
They recall strong product cultures where product managers, designers, and engineers were all close to customer discovery, so ideas could be built on regardless of who created the first prototype.
When customer understanding sits with a small group, ideas get handed down and context is lost.
AI can make that process faster, McHugh argues, but cannot make it better.
Teams need a foundation of real customer understanding, including genuine Jobs to Be Done work rather than a user story template.
For brands planning a campaign
An advisory engagement around AI could focus on whether a team has the customer understanding to use AI prototypes well, rather than treating tool rollout as the goal. A venture capital firm could use this as a signal when evaluating how a portfolio company adopts AI without weakening product judgment.
Practical diagnosis of stalled renewals and adoption3
Customer research through Jobs to Be Done
McHugh treats Jobs to Be Done as an operational method for product and go-to-market decisions, not a template.
Read more
They describe moving from overwhelming stakeholder feedback to focus by talking to people who made a decision, asking about the events leading up to it, and listening for forces pushing for and against it. They cite Bob Moesta's saying, "Bitching ain't switching," and distinguish demand problems from the annoying problems that surface first in interviews.
Decision interviews: recruit people who switched or renewed, map the events leading up to their decision, and separate complaints from the forces that drove action.
For brands planning a campaign
A brand can assess whether McHugh turns customer interviews into a shared decision framework for product teams. For a venture capital advisory role, useful evidence is whether they push portfolio companies to test demand assumptions before funding a roadmap or sales plan.
Across several posts, McHugh argues that the hardest EdTech problems sit outside the product, in interconnected incentives, funding, procurement, district relationships, and teacher experience.
Read more
They reference Donella Meadows' Thinking in Systems and a healthcare discussion to argue that changing parts without changing structure lets the system snap back. They warn that shipping features quickly can be a guess dressed up as progress without a hypothesis about how the system produces student outcomes.
For brands planning a campaign
A brand can assess whether McHugh would help a portfolio company map its buying and adoption system before investing in new features or go-to-market. In a strategic advisory role, their value would be spotting when a product problem is actually about distribution, procurement, or incentives.
McHugh writes about EdTech companies that start mission-led and drift toward revenue or board-facing numbers.
Read more
In one post, they describe being asked to build financial projections for an undefined solution.
In another, they trace a path from a social impact program to an EdTech startup to a nonprofit and list demand clarity, holistic measurement, governance, system understanding, and funding as areas to balance.
They say motivation slips when mission and rewards diverge.
For brands planning a campaign
A brand can assess whether McHugh would ask hard questions about incentive alignment inside a portfolio company. For an EdTech investor, that matters when mission language obscures commercial or measurement gaps.
McHugh is skeptical of AI turning designers into judges of PM-generated prototypes.
Read more
Drawing on a UX and product management background, they argue that AI can speed up visualization but cannot replace shared customer understanding across product, design, and engineering.
The strongest teams they describe work like improv, with each role building on the others' ideas.
They warn against reducing Jobs to Be Done to a user story template.
For brands planning a campaign
A brand can assess McHugh's view on how AI changes product roles and whether they can help a team keep customer context shared as prototyping speeds up. For advisory work, they would likely push for research foundations before tool adoption.
Practical diagnosis of stalled renewals and adoption
In a post about an EdTech product leader, McHugh describes renewals stalling as leadership reaches for pricing, seasonality, or competitor explanations.
Read more
They argue those answers are plausible enough to stop inquiry.
The real work is finding the demand problem behind the easy complaint by using a different lens on interviews, not simply having more conversations.
They also mention untangling product strategy after platform mergers and pilot-to-district adoption stalls.
For brands planning a campaign
A brand can assess whether McHugh diagnoses commercial slowdowns with evidence rather than accepting convenient explanations. For a venture capital firm, that matters in diligence and post-investment support when a portfolio company's retention or expansion softens.
McHugh's public output mixes personal essays, book reflections, event takeaways, and practical product arguments.
Read more
They use family stories to explain motivation, conference moments to explain Jobs to Be Done, and reading notes to connect mission and measurement. They name people and institutions they learn from, including Bob Moesta, Jim Kalbach, Halle Tecco, and the Clayton Christensen Institute.
For brands planning a campaign
A brand can judge whether McHugh's LinkedIn voice suits an advisory or thought-leadership partnership. Their argument-led, example-rich posts suit an audience of product leaders and investors rather than a broad consumer audience.
McHugh describes moving from computer science to UX to product management, then into independent work with EdTech teams.
Read more
They write about being a fractional product leader, coaching product managers through Supra, working with early-stage founders through Volta, and wanting to work with leaders willing to examine gaps between mission and incentives.
For brands planning a campaign
A brand can assess whether McHugh's independent advisory experience matches its portfolio needs and whether they are candid about what useful work requires: leaders willing to examine evidence and incentives.
McHugh's posts show no sponsorships, affiliate arrangements, or businesses they own.
Read more
Their brand connections are professional and educational: they coach product managers with Supra, spoke on stage at EdTech Week, took part in programming from the Clayton Christensen Institute and UPenn's Center for Social Impact Strategy, and have worked with Volta start-up founders.
Their posts also describe several earlier employers—a for-profit company, an EdTech startup, and a non-profit—without naming them.
Ask for those employer names.
Supra
Disclosed partnership
McHugh writes that an introduction led to a recommendation to coach with Supra, where they support product managers.
Read more
Ask whether they are employed by Supra or work with it as an outside coach.
McHugh attended a webinar Halle Tecco gave through the Clayton Christensen Institute, followed by office hours with Ann-Somers Hogg and Ann Christensen.
Read more
They say the institute's conversations continue to shape their thinking on innovation in education.
McHugh says a Slack-group connection with Matt Cooper led to working with Volta start-up founders, shaping how they now work with early-stage companies.
Beth McHugh writes about why EdTech products succeed or stall.
Read more
Their posts return to factors outside the product: how customers make decisions, how a district’s funding and procurement work, and whether a team shares enough customer understanding to build together.
Start with the Jobs to Be Done posts, where McHugh describes talking to people who have already switched rather than collecting complaints.
Then read the systems-thinking pieces, which argue that improving features without changing the surrounding structure lets the system snap back.
The mission-and-incentives posts explore the gap between stated purpose and what gets funded.
McHugh’s argument-led, example-rich writing draws on family stories, conference takeaways, and book reflections to make product points; following an argument across several posts offers more than reading any one entry as a summary of their views.
Jobs to Be DoneSystems thinkingEdTech product strategyCustomer researchMission and incentivesProduct managementDesign and product collaborationWritten postsBook and talk reflectionsEdTech product leadersProduct managers
Melissa Johnson
Johnson writes about K-12 and EdTech sales from the operating side of the problem McHugh describes from the product side.
Read more
Both treat a district’s funding cycles, procurement steps, board calendars, and quiet champions as conditions that shape outcomes more than any single tool or pitch.
Johnson’s post on responsive buyers who are still risky forecasts asks sellers to check who owns the decision, whether funding is identified, and what evidence comes from the district rather than a champion.
It’s the sales-execution version of McHugh’s distinction between demand and complaints.
Both also build a post around a concrete story before drawing the professional lesson.
Johnson focuses on sales leadership and forecasting discipline, using an AI-supported review method.
McHugh focuses on product strategy and customer research, using decision interviews and Jobs to Be Done.
Follow Johnson for pipeline and deal-inspection thinking; follow McHugh for product and demand-side diagnosis.
Terry and McHugh both argue that buying or deploying software is not the same as producing change.
Read more
The real difficulty lies in the operational reality a district has to live with.
Terry’s teacher-evaluation posts describe how two principals can rate the same lesson differently, attribute that variability to interpretation rather than intent, and argue that leaders need confidence in the basis for a rating before finalizing decisions.
That echoes McHugh’s claim that EdTech’s hardest problems sit one level above the product, in incentives and structures, and that shipping a feature without a hypothesis about outcomes is a guess dressed up as progress.
Terry works in the high-stakes field of teacher evaluation, including TIA-aligned models where small rating differences affect compensation and designations.
Her posts address district leaders facing summatives.
McHugh takes a broader view of product and systems strategy across EdTech.
Follow Terry for evaluation, rating defensibility, and teacher-retention policy; follow McHugh for product diagnosis and demand research.
Lapis and McHugh both moved into product work from other backgrounds, put customer understanding ahead of the artifact, and connect design decisions to access and equity in education.
Read more
Lapis describes a ten-year career in language instruction and community building before UX, then presents Studywavve, a student-collaboration app with onboarding, filtering, scheduling, and feedback features.
The stated aim is to make education equitable for students with limited access to materials.
That blend of firsthand classroom experience and concrete product detail recalls how McHugh draws on their EdTech and product history to argue that teams need shared customer context before prototyping.
Lapis presents individual design projects and builds a craft portfolio, including a candid post about the difficulty of getting an entry-level role.
McHugh writes about team and organizational strategy, using Jobs to Be Done and systems thinking as operating methods.
Follow Lapis for design systems, inclusive design, and an early-career product perspective; follow McHugh for product strategy and research methods.
The LinkedIn following is about 3,400 people, observed on October 7, 2026, alongside ten posts Beth McHugh published between October 2025 and September 2026.
Read more
That shows a real, if modest, professional following on one channel, but not who is in it.
Geography, age, seniority, employer type, and job function are unmeasured; treat the follower figure as a size signal, not a composition one.
The posts show a narrow, consistent content focus: EdTech product work, including Jobs to Be Done interviewing, the gap between mission language and revenue incentives, systems thinking about districts, funding cycles and procurement, why roadmaps and curricula fail when reality diverges from the plan, and how product, design, and engineering should share customer understanding.
Several posts address people inside EdTech vendors or districts, focusing on stalled renewals, unclear demand, and leadership pressure.
The implied reader is an EdTech product leader or founder, not a general business audience.
A strategic advisory engagement would be pitched to roughly that group.
A following of this size supports an advisory or peer-credibility role, not a distribution buy.
Ask them for a recent audience breakdown—geography, role or seniority, and employer type—and engagement figures for a handful of posts on the same themes they would cover in the proposed strategic advisory engagement.
If they have run an audience survey, request it for job title and seniority, since platform data alone will not answer those questions.
Beth McHugh's posts do not include a sponsorship offer, media kit, rate information, or partnership inquiry route.
Read more
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.
The strongest fit is an EdTech venture capital firm hiring Beth McHugh for strategic advisory work or diligence support.
Read more
Their posts address questions portfolio companies face: whether renewals are stalling because of a real demand shift or a convenient explanation like seasonality; whether a product solves a problem rooted in district procurement, funding cycles, and teacher experience; and whether mission language still matches what gets funded.
In one post, they describe being asked to build financial projections for an undefined solution, with no evidence behind the numbers.
They pushed back because the board needed a story—a direct signal of how they respond when a portfolio company wants a plan to look settled.
Another fitting need is a working session for an EdTech product team overwhelmed by feedback and in need of a method.
They describe talking to people who made a decision, mapping the events before it, and separating complaints from the forces that caused action, citing Bob Moesta's line that complaints do not prove someone will act.
Their LinkedIn following is around 3,400, so the fit is peer credibility and advisory judgment rather than distribution.
Hire them for their method and willingness to challenge a plan, not their reach.
When to choose a specialist
A paid sponsorship or co-marketing campaign is a poor fit if it requires a published format, rates, and a public inquiry route.
Read more
The posts contain no sponsorship offer, media kit, rate information, or partnership inquiry process, so buyers should expect to make direct contact.
Ask for rates and available formats before planning a campaign.
A broad-audience consumer or general business campaign is also a poor fit.
Every post focuses on EdTech product work: Jobs to Be Done interviewing, systems thinking about districts and procurement, mission and revenue drift, and how product, design, and engineering share customer understanding.
The writing targets EdTech product leaders and founders.
A budget aimed at a general audience or buyers who do not think in terms of product decisions would work against the content.
Another mismatch is a campaign that presents fast feature shipping as progress.
Their clearest position is that without a hypothesis about how the surrounding system produces outcomes, every shipped feature is a guess dressed up as progress.
A campaign that treats shipping volume as the message would contradict their published view.
A worked campaign example
Take an EdTech venture capital firm with a portfolio company whose district renewals have softened.
Leadership has settled on an explanation: seasonality and a competitor.
The firm brings Beth McHugh in for a short diagnostic engagement rather than accepting that answer.
In week one, they reframe the question.
The company's account team has heard complaints about onboarding and reporting.
They treat those as annoying problems—the friction people name easily—not the demand problem that caused the switch.
Their method is to interview people who made a decision, both districts that renewed and those that looked elsewhere, and ask about the events leading up to the choice rather than what they wanted.
They listen for forces pushing toward and against the decision.
In week two, they map the system around the product.
The district adopted it for consistency across schools; teachers experienced less autonomy and more work.
The renewal looked strong in a board deck while the classroom experience told a different story.
They lay out the surrounding pieces, including procurement windows, funding cycles, and campus-level support, and identify where the product is optimizing one part while the structure holds the outcome in place.
In week three, they deliver a short set of findings to the investment and operating leads: which accounts moved for demand reasons, which for seasonal ones, and what evidence would show the difference.
They propose two or three bets tied to leverage points in the system rather than a longer feature list.
The deliverable is a decision aid, not a plan to be defended.
The firm can judge the engagement by whether the portfolio company starts asking better questions—such as what evidence would show the hypothesis is wrong—instead of restating last quarter's roadmap.
Choose Melissa Johnson when the advisory question is whether a K-12 sales organization's forecast can be trusted.
Read more
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.
Her posts focus on sales execution and sales leadership, not product demand research, Jobs to Be Done interviewing, or how district funding, procurement, and classroom experience shape adoption.
A firm trying to understand why renewals or adoption changed would get a forecast-inspection view, not a diagnosis of underlying demand.
Her posts do not describe advisory or diligence engagements, so assess her on sales leadership practice rather than venture advisory work.
Choose Shannon Terry when the diligence question concerns teacher evaluation, TIA-aligned incentive models, or implementation within district constraints.
Read more
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.
The scope is narrower than the advisory question.
The posts focus on teacher evaluation, evaluation consistency, and K-12 leadership; they do not address Jobs to Be Done method, broader product strategy, or mission and revenue governance.
A firm evaluating product philosophy across a portfolio would get one vertical's implementation perspective, not a general demand or systems diagnosis.
The two posts are short promotional and thought-leadership pieces, not extended analysis.
Choose Staci Lapis when the question is about early product design craft and the practitioner's view of a student-facing product.
Read more
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.
The posts reflect an early-career stage: one asks for help finding an entry-level role and lists open-to-work availability; the other introduces a personal project.
They do not describe advisory, diligence, or commercial strategy work.
Both predate the rest of this page's material by more than two years.
A firm would gain a design and classroom-practitioner perspective, but should ask for current work demonstrating demand analysis, systems mapping, and mission-and-revenue judgment.
