Marvin McTaw (@mmctaw) header
Marvin McTaw (@mmctaw) profile picture

Views are my own and helping @sched grow to bigger heights

Atlanta, GA
Joined December 2008
Photo by Marvin McTaw (@mmctaw)Photo by Marvin McTaw (@mmctaw)Photo by Marvin McTaw (@mmctaw)Photo by Marvin McTaw (@mmctaw)Photo by Marvin McTaw (@mmctaw)Photo by Marvin McTaw (@mmctaw)Photo by Marvin McTaw (@mmctaw)Photo by Marvin McTaw (@mmctaw)Photo by Marvin McTaw (@mmctaw)Photo by Marvin McTaw (@mmctaw)
How many hours does your team spend after the big PD day just reconciling paper sign-in sheets?
7
How many PD sessions does your district run outside the one big annual event? Genuinely asking.
4
How many of your vendor deals stall on security review instead of price? Ours do too. I stopped seeing that as a delay a long time ago.
1
8
How do you tell signal from noise in customer feedback? If it's the fourth time you've heard it, it's signal. If it's the first, it's still just an opinion.
1
14
If PD hours only show up after they're finalized, when does a coordinator actually know where their staff stand for the year?
1
4
It's summer institute season. Somewhere right now, a coordinator is manually matching 400 teachers to session choices by hand. There's a faster way.
1
5
Genuine question: how do you know when a team has actually moved from chaos to systems? For us, it was the day the complaints got boring.
3
What did teachers RSVP for at your last PD day that you haven't offered again since?
2
Sales standup this week: one $10k deal closed, a stack of follow ups, and zero new feature requests. The absence of new ideas told me more than a week of new ones would have.
1
12
Before: chaos on our CS team, something on fire every day. After: 'ugh, another 4 hour meeting.' If your complaints got more boring, you probably built something that works.
8
A year ago, "if we lose the sign-in sheet, we're toast" was just a comment on a sales call. This summer, it's a feature we're shipping.
7
Google Forms isn't the problem. Using it to sort 400 teachers into concurrent sessions is.
3
The big institute: polished, professional, organized. The building-level workshop next month: a spreadsheet and a prayer. Same district. Same platform sitting unused.
2
PD coordinators don't need fancier name tags. They need badges that do the sorting for them.
3
We designed pricing that made sense to us, not to how districts actually run PD. That one's on us. We're rebuilding it now.
5
Old model: one big PD day a year on Sched. New model: every PD event on Sched, all year. Our hours reporting is still catching up to the second one.
3
Old model: pay per event, use us once a year. New model: pay for seats, use us whenever your PD calendar needs it. We're mid-rebuild right now.
3
First time planning the district institute. No experience. No system. Just print outs and long nights. Sound familiar?
4
This should've existed a year ago. We built session scheduling before we built speaker visibility. Backwards, but fixed now.
8
First PD days of the year are unforgiving. No margin for a speaker who ghosts. Try Sched free: hubs.ly/Q04t7KLv0
3