Design For Responsiveness

Your teams are all capable, and all on different paths. Rather than try to predict their needs, we want to be responsive. We want to be helpful when they need us. We want to get out of the way when they need to execute.

We recommend an enabling, responsive approach, rather than trying to predict their needs or impose a procedure.

It's easy to imagine how teams will progress through each week of your accelerator, learning from customers, mentors, investors, building a product, then learning to pitch; and we can even envisage how we can move from one topic to the next, week by week. All very orderly.

In reality, every team will choose its own path, and attempts to predict their needs beyond the first few weeks cause frustration. If you've run an accelerator before, you've experienced how founders retaliate against scheduled activities they don't find helpful. They just want to get on with their company.

Often, it makes sense to schedule placeholders for workshops and mentors, so founders can schedule their lives around those times without conflict, and you can fill them with relevant help as needs arise.