Skip to main content

Design Sprint and Dual Track Development

Context

The current typical model of starting a large program is to have a discovery workshop for the program followed by detailed project inceptions. The project inceptions are spaced and detailed.

There are not a lot of discovery workshops we do that is mutual discovery. It is more of sense making of an earlier discovery process.

The Pitfalls and some thoughts

With the discovery process feeding into the project Inceptions was great. it gave direction. However, validation of the direction based on feedback from projects seems to be missing.

The reason the feedback is missing is 2-fold:

#1 - The discovery workshops don't seem to have a cadence with the project Inceptions

#2 - The team that does discovery workshops is to involved with the project inceptions and vice versa,


Some Thoughts around the problem statement

  • Not all the discovery workshops are sense making.
    • Yes not all of them. We have had the opportunity to work with clients that have involved us in their discovery process. 
  • Not all discovery workshops use a separate team.
    • Yes, The project team is involved with discovery as well However, the typical structure has been that the discovery workshops tend to morph into a program inceptions.
    • Post that, we plan one or more project inceptions. This process does not allow us to have the project teams involved in discovery since the project teams come in a lot later than the discovery workshops.
  • Why do you think feedback needs to go from project inceptions to discovery workshops
    • What we find during our project execution is also important to consider for the program direction. This might influence other projects in the program as well and hence is important to feed into the discovery process to set the right direction.


A few Ideas discussed

  • How do we provide feedback from Project Inceptions to discovery workshops?
    • Since the cadence for a discovery workshop is pretty long, the feedback takes time to percolate back. The best way for us to accomplish this is to have a cadence that is parallel to the Project execution.
    • We discussed the Dual track development model as discussed by Jeff Patton. We used the picture below for our conversation: http://jpattonassociates.com/dual-track-development/



  • What are the Key thoughts of Dual Track Development? [Shamelessly copied from the website]
    • Discovery and development are visualised in two tracks because it’s two kinds of work, and two kinds of thinking
    • Discovery is a necessary part of product development. Practice it with the same agile and lean principles in mind.
    • If we’re doing discovery right, we substantially change and kill lots of ideas.
    • While a product manager, designer, and senior engineer may lead and orchestrate discovery, they must involve the whole team in discovery tasks wherever possible. Keep discovery work and progress visible to the whole team.
  • Is this going to be time - consuming? It typically takes a good amount of time setting up the discovery workshops?
    • Yes it does take some time. We can draw some inspiration from the Design sprint concept that Google venture uses. More information here: gv.com/sprint/
On Monday, you’ll map out the problem and pick an important place to focus. On Tuesday, you’ll sketch competing solutions on paper. On Wednesday, you’ll make difficult decisions and turn your ideas into a testable hypothesis. On Thursday, you’ll hammer out a high-fidelity prototype. And on Friday, you’ll test it with real live humans.

Comments

  1. Thank you for posting such a great blog. I found your website perfect for my needs. Read About Design Sprint Online

    ReplyDelete

Post a Comment

Popular posts from this blog

Organizational growth and turn over

Organisations need to grow. However, they should not grow for the sake of growth. That would be a virus. Orgs should not grow to survive as well. Orgs should grow with a purpose.

From Idea to reality - The progress of an Idea

 I have been thinking of writing a simple app for locating trash cans at Chennai. The first thing anyone would do was to see if the idea has been already implemented. Sure enough, it has been. This is the app - Check it out. http://trashithere.herokuapp.com/ When I tried using the app, I found out that there were only few trash cans. This was a crowd sourced application. I guess this app was not used much. The Spark This led me to questioning myself - What problem led me to this application. I yearned to live in a place that was clean. My assumption was that if people found places to throw thrash, they would not litter. Going ahead with your idea

Counterfiet goods and the fledgeling e-commerce market places

India has a nascent and a very active market place. With good interest, the right climate for growth and right product mix, the indian retail marketplace seems to be going places. However, there are some alarming signals that seem to be ignored for growth that have a good chance of being dangerous to all the stakeholders involved. The issue I am talking about is the sale of counterfeit goods in all the indian market places. India has not had a history of strong Intellectual property rights. This time it is getting messier. The Indian marketplace model is very interesting and suits well to a country as diverse as India. The market place model floated by all the major e-railers suits the fact that the seller and the buyer can be connected for serving the needs for every day goods that are not necessarily covered by IP laws. India needs more effective IP laws since it is struggling with some products like traditional indian products that cannot be covered by IP versus modern produc...