7 ways to infuse the scrum team with research findings

I’m lucky. My main scrum team really want to understand who we are building stuff for, and how the stuff fit into those users’ lives.

But not all individuals in the team like to learn about our users in the same way. Also, learning science tells me that repetition is the foundation of remembering. And I believe that engaging with the same material in different forms increase understanding. 

Therefore I bring what I learn in design research to each team mate in different ways: 

  1. My team mate can participate in the research – by listening in to the call or even leading the session
  2. My team mate can help me analyze each research session – mapping, transcribing, or such 
  3. My team mate can hear me, during standup, tell an exciting story from yesterday’s research session 
  4. My team mate can help aggregate the individual sessions into insights and communicate those to the rest of the team 
  5. My team mate can hear the overall insights, perhaps as part of the startup of a new initiative/epic 
  6. My team mate can hear the specific findings that inform a single story as we work together to write and groom the story 
  7. My team mate can hear the specific reasons for our design choices when the team mate is about to start work on a story 

Obviously not everyone in the team engage with every piece of research in all these ways. That would be so overkill. But all my mates engage with research in some or these ways. Which ways depends on the research question and the preferences of each team member.

Which is the best way to craft digital products?

It might be that I’m a crappy designer, but I never create something on my own that is as good as something that I have crafted with someone else. I co-create with Charlie, Sabrina and Nasia

From ”Let us build” to ”Let us understand (and maybe build)”

Sometimes a project is started based on a feeling that a designer, engineer or manager has. However, what we choose to build should be "directed" by our users. Is there a way of getting user driven in a project that started based on internal feelings? I think Krste has found a way!