Teacher-powered professional development
Mentorful pairs your teachers, gives them a structure for coaching each other, and measures whether your faculty is actually getting stronger. You see where growth is happening across the building, by department and by focus area, while the year is still in motion.
Serious professional learning. Surprisingly little administration.
50 teachers · 20 active pairs · 72% cross-department
What makes it work
Most schools have tried some version of teachers helping teachers. It usually fades. These three are the reason it doesn't here.
Coaching runs teacher to teacher, with no ratings and no rubric anywhere in the product. When nothing is being scored, teachers tell the truth, which is the only condition under which any of this produces real data.
You see trends by department, grade level, and focus area. Patterns, never names. No individual response reaches you, and that is not a setting anyone can switch off.
Pairings, meeting rhythms, and focus areas run on their own. Your time cost after setup is reading the report.
The premise
Your building already contains most of what your teachers need. Someone has solved the transition problem. Someone has a feedback routine that works. Someone knows exactly how to reach the student everyone else has given up on.
That is institutional wisdom, and every school has more of it than it can currently use. Today it moves when two people happen to be free at the same time, and it stops at the department door.
Mentorful makes it deliberate. Who talks to whom, how often, about what, and what happens to it afterward. Nothing gets imported. It is your faculty's own expertise, put into circulation on purpose.
Why it matters
Collective teacher efficacy is a faculty's shared belief that together they can move students, including the students who are hardest to move. In John Hattie's synthesis it outranks every program, every curriculum, and every incentive structure ever measured.
Donohoo identifies where it comes from: succeeding together with a hard class, watching a colleague pull something off, hearing credible encouragement from someone whose opinion you respect, and working somewhere that isn't anxious or isolating.
Every one of those happens between colleagues.
You cannot inspire a faculty into it. You build the conditions that produce it, and then it shows up.
What it rests on
Not on an org chart. In practice, on a Tuesday, when a lesson goes sideways and someone needs to ask.
A teacher who cannot say "that didn't work" learns nothing from the person next to her.
A faculty needs common language for good teaching, or every conversation starts from zero.
Research on social capital calls these the structural, relational, and cognitive dimensions. They are the foundation the enabling conditions stand on. Mentorful measures all three, then does something about each one.
The five enabling conditions
Donohoo, J. (2017). Collective Efficacy: How Educators' Beliefs Impact Student Learning.
Defensibility
Standardized results tell you what happened twelve months ago, shaped by a dozen things well outside your control. By the time they land, the decisions they should have informed are already made. In the meantime you are running a building on instinct and hallway impressions.
Your faculty's structure in September and again in January. What changed, what didn't, and which departments connected.
Every panel exports as an image. Your school's name on it, your teachers' data behind it, no redrawing.
Every number came from your own teachers, anonymously, using the same twenty-six items both times. Nothing modeled, nothing projected, nothing benchmarked against a district you've never met.
Boards don't fund promises. They fund proof.
Compatibility
An outside expert comes on a scheduled day. The binder goes on a shelf. When the contract ends, so does the capability, and next year you buy it again.
Your best veteran teachers and your strongest new hires are already on payroll. That expertise doesn't walk out at the end of the session, and it gets deeper every cycle.
You already have PLCs. You already have an initiative you're rolling out this year. Mentorful isn't a replacement for either. It's the layer underneath that makes them work.
PLCs stop being formed by department or by whatever seemed urgent in August, and start forming around what teachers were already struggling with. An initiative stops traveling through email and starts traveling through people, because you can finally see who is actually connected to whom.
Nothing gets cancelled. Nothing new goes on the calendar.
How it runs
Built from your own faculty data, cross-department wherever possible. The math teacher and the English teacher have more to teach each other than two math teachers do.
Every few weeks, twenty minutes. Partners talk about what's actually going on, and it gets captured as they go.
A few times a year, into each other's rooms. Strength finding, visioning, more and less, obstacles and assets. One shared record, written together.
Conversations get tagged by domain. Domains accumulate. The faculty's real priorities become visible without anyone guessing.
We are not evaluating teachers. We are identifying promising practices.
That distinction changes everything about how it feels when someone walks into your room.
Where it goes
Most schools form professional learning communities by department, or by whatever seemed important in August, then hope people show up with something to work on. Mentorful routes them from what teachers were already talking about.
A teacher whose conversations kept landing on transitions and grouping walks into a Clinic PLC with three colleagues who landed in the same place. Nobody assigned that. It came up out of the work.
What leadership sees
Every school in your district can tell you its test scores. Almost none of them can tell you how their teachers are actually connected, what the staff is working on right now, or whether that changed since September.
What it actually moves
RAND's 2026 district panel puts budget shortfalls, keeping effective teachers, and school climate at the top of the list. Here is where Mentorful touches them, and where it doesn't.
What we measure. Collective efficacy is the single strongest predictor of achievement in Hattie's synthesis, which is exactly why it is worth building on purpose rather than hoping for. What Mentorful measures directly is your faculty: how it is connected, how much trust it carries, and whether that moved between September and June. We measure the thing the research says drives the outcome. We will not hand you a test score and take credit for it, because achievement moves through a dozen things at once and honest attribution takes longer than one semester. Show us a faculty that got more connected and more candid, and the rest of the evidence is on our side.
Data and privacy
Mentorful was designed by a classroom teacher, and the boundaries are architectural. They are not permission settings an administrator can switch off, which is what makes them easy to explain to a faculty, a union rep, or a district data officer.
Responses are stored against a random identifier that is never linked to a login. Only aggregate patterns exist in the system. This cannot be changed.
Journal entries are visible to the two teachers who wrote them and to nobody else, including leadership.
There are no ratings, no scores, and no rubric anywhere in the product. There is nothing to score and nothing to appeal.
Domain data reaching the admin dashboard is aggregated and anonymized. You see what the faculty is working on, never who raised it.
What a co-mentor can see about a teacher's working style is set by that teacher.
Full export at any time, defined retention windows, and no student data in the system at all.
The pilot path
You don't need a district-wide decision to find out whether this works. Start in one building, follow the data, and let the report make the case at your next board meeting.
We'll tell you which engagement fits, and we'll tell you if the answer is not yet.
One school, one semester, nothing new added to the schedule.
Same instrument, same faculty, end of the semester. You see what moved and what didn't.
Walk in with an impact report built on your own teachers' data.
If the second scan shows nothing moved, you'll know that from your own faculty, and you can stop. That's the whole risk.
What we offer
Where your faculty stands: structure, relationships, shared knowledge, collective efficacy. Full network report and a findings session.
A workshop that gets a faculty to see itself. Teachers leave with a partner and a first conversation scheduled.
Co-mentoring as the infrastructure a rollout travels through. Early adopters paired with skeptics, deliberately.
Six weeks, cohort-based. Clinic, Toolbox, Task Force, Data Dive, with a portfolio of facilitated sessions.
Read a network report, interpret what it says about your faculty, make decisions you can defend.
Longer-horizon work across a leadership team or a district. Network architecture and internal capacity.
Every one works on its own. Together they build. Tell us the shape of your year and we'll tell you where to start.
Where this work has been
Go Sideways! A ninety-minute workshop on co-mentoring and collective teacher efficacy. Full room, and attendees asked for the deck to run the activities with their own faculties.
Session on co-mentoring methods to build teacher collective efficacy.
Faculty workshops and shorter engagements with schools that wanted the conversation before the platform. Full-cycle partnerships begin this year.
It builds collective intelligence: a faculty that knows more together than it does apart, and keeps getting better at it. It is effective, it is inexpensive, and it runs on time you already have and knowledge you already own.
And teachers enjoy it, which is not a small thing in a field where most improvement efforts are endured.
Your building already has what it needs. You're the one who can put it in motion.
Start with one department if you'd rather. One semester and you'll know from your own data either way.
Mentorful