Building Educator Communities That Inform Product and Support Adoption
How educator feedback shaped a student report, and how community and in-app guidance helped customers use the tools they already had.

At a glance
The challenge
Educators using assessment and intervention tools have to make decisions quickly. Is a student on pace? Where are they getting stuck? What should I do next? Across New Classrooms, CTB/McGraw Hill, and Savvas Learning, I worked on those questions from three angles: listening through advisory boards, building communities educators had a reason to return to, and offering guidance inside the product.
The insight
The most useful feedback was often about a decision an educator needed to make. At New Classrooms, our advisory council helped us see what teachers wanted from the Individual Student Report in Teach to One Roadmaps. Was the student on track to master two skills that week? If they were falling behind, which skills were giving them trouble? We brought in additional student data, prioritized the information teachers needed for a quick progress check, and made more detail available through drill-down.
See the Individual Student Report in the January 2026 Roadmaps Roundup.
At CTB, advisory board feedback ranged from broader concerns about security to details as specific as whether a graph line should be blue or green. Both kinds of feedback helped us understand what mattered to customers as they used the product.
At New Classrooms, advisory council members also helped us bring Roadmaps to life by writing about how they used it in their own classrooms. In one story, David Krulwich shared how his Bronx middle school gave students more ownership of their math learning.
See more educator stories and newsletters in my Content Samples.
Putting the strategy to work
Build a community around the customer’s next step
At CTB, I built a workflow that welcomed new Acuity users, invited them to join the community, and guided them through onboarding with information relevant to where they were in their product journey. The community gave educators somewhere to turn as their questions changed over time.
At Savvas, I designed a workflow that let customers move naturally through the process, asking for information only when we needed it to give them a better experience. The broader community relaunch and self-service work gave educators a clearer path to support.

Offer help where the question comes up
At New Classrooms, signing in to Roadmaps or visiting a specific page could trigger a notification pointing educators to a relevant knowledge-base article. At CTB, we also used prompts to connect educators with articles about features they were starting to use. The timing mattered. Educators could find the explanation while they were working with the feature and put it to use right away.
Measured outcomes
CTB’s Acuity community grew to more than 20,000 members and drew about 5,000 visits and 40,000 views per month. At Savvas, self-service support cut cases by 50% and reduced agent handling time by four minutes per ticket.
What I learned
An advisory council is most valuable when you can point to a decision it helped change. A community earns its place when educators can use it to do their jobs. I use both to understand where customers need help, then bring what we learn back into the product, onboarding, and support.