Design sprints have seen massive adoption in the past few years, driven by widely available resources and enthusiastic communities of practice. As our collective practice grows, their utility as a problem-solving tool has grown, too. People are experimenting with adaptations to take on bigger and more complex challenges, as was evidenced at a recent Design Sprint conference here in Paris, where one sub-theme was titled ‘One sprint is not enough’.
My own experience includes challenges like vision setting and org design, with configurations from two hours training sessions to elongated two week versions and everything in between, working with a tiny team in a sunny garden to 70 people in a hotel ballroom. …
In the past few weeks Paris has had big grey skies with fleeting moments of clear blues and bright sunlight, while still remaining cold and rainy. It’s not spring yet, regardless of the increase in pollen that’s starting to make me sneeze.
A brighter beam of sunlight was an observation by my AQ colleague Sachiko about client onboarding, which led to clearer thinking about the essence of onboarding — it’s an invitation to join a journey — and how we might better design for it.
Why are we here? It’s a question that we keep coming back to in all kinds of contexts, and yet, manage not to answer in a clear-enough manner, even in specific ones like kicking off a project. But if we considered how each member needed to be invited into the conversation, perhaps momentum would become simpler to build. …
The ResearchOps community organises remote town hall sessions to explore different perspectives of #ResearchOps. For the 4th edition, we had the pleasure of welcoming Arnab Pal from Clinton Health Access Initiative.
Drawing on lessons from a recent study undertaken in rural Punjab with Hepatitis C patients, Arnab presented the challenges of organising and conducting research along with the iterative models used to stay nimble and agile during the exploratory and deep-dive phases in sensitive zones.