Turning an e-learning platform into program management software for KU Lighthouse.

When KU Lighthouse looked at joining Tools, Accelerace’s e-learning platform for startups, I led the discovery with their program managers.

The problem

I interviewed KU Lighthouse’s program managers, and they walked me through their entire process. Booking meetings, keeping notes and following up all happened manually, through emails and messages. They often didn’t know a new startup had joined until it got in touch.

Their notes on each startup were personal and fragmented, and everyone kept them differently. When a startup moved to a new program or mentor, the notes couldn’t follow it, and important learning moments and feedback were lost along the way.

The solution

This led me to design a meeting system where startups and program managers book sessions with each other, keeping the notes, conversations and history from every meeting in one place. Program managers set when they’re available. Startups book them, or they book the startup.

Setting availability: available hours from 8:00 to 14:00, every Tuesday, Thursday and Friday, with a switch to let startups create an event directly in your calendar
Setting availability, empty and filled in
Book session: pick a date in February 2024, then a timeslot on Tuesday 9 February Confirm the 13:30 to 14:00 timeslot, then Session is now booked, with a calendar event and a Zoom link
Booking a session, from picking a date to the booked meeting

Booking a meeting also became a step in the startup’s phase progress. Startups and program managers see the same steps, so program managers can see who has booked and add steps of their own.

Startup Phase Progress, the program manager’s view: the current phase at 50%, with booking a meeting and preparing a pitch deck ticked off, a follow-up meeting added by the program manager, and an Add step button Your Progress, the startup’s view of the same phase and steps
Phase progress · the program manager’s view, and the startup’s

With every meeting and step now on the platform, we could act on them. We built a more flexible automation foundation, so program managers can set if/then rules and follow-ups happen without chasing every startup by hand.

Editing the Welcome widget: if the Getting PMF learning path has been completed, hide Learning paths from the dashboard
A condition on the startup dashboard’s welcome widget

Outcomes

KU Lighthouse became a paying customer. The meeting system went out to all of Accelerace’s programs, and Accelerace came to rely on the automation flows for its own emails and meeting setup.

Reflections

A central lesson was keeping the focus on the foundational software, and figuring out how each customer’s needs build on top of it. Rather than making individual features tailor-made for each client, I learned that it is much more scalable to consider the wider tech stack, platform and strategy, and align them into a product that helps multiple user groups at scale.

I also enjoyed getting a different perspective. Seeing how fundamentally different KU Lighthouse’s flow was sparked new ideas about my own approach to the Tools platform.