Tuesday, February 23, 2016

Design the Poster

Anyone that's been around Agile for a while has probably heard of the Design the Box exercise. The idea is to help the team define and understand the product vision.

I'm getting near the end of a project. We've had some challenges in terms of making the right decisions on scope. This has manifested itself in completing user stories only to have the business team say "I know that's what I asked for, but I don't think it's right." We didn't do a Design the Box at the start of the project.

However, as they start implementing their organizational change management approach (this tool is going to a large set of users), they are developing some communications tools including a web portal and a set of posters. These posters are 2x3 feet, have a logo and the tool name on the top, and more information below. They are going to be posted around the buildings where the target end users work. As I looked at this it hit me, if we had created this poster at the start of the project, we may have avoided some of the challenges we encountered.

So next time you're starting a project, think about what the poster might say.

Friday, February 05, 2016

Are You Experimenting?

I came across another interesting idea in Change By Design. It was presented as Toyota's ideas around training and had 4 principles:

  • There is no substitute for direct observation
  • Proposed changes should always be structured as experiments
  • Workers and managers should experiment as frequently as possible 
  • Managers should coach, not fix

This idea of experimenting caught my attention. So often as I'm designing a solution for a customer, they want to try to get the perfect solution first time out of the box. When they don't know what perfect is, they struggle to make decisions. I can recall one client, after 3 weeks of developing a complex interface, others looked at it and we went through another 3 weeks revising it. This was all in development, the real end users didn't have a chance to try it out. No experimentation at all, just managers trying to guess what was needed. No direct observation.

This is just one example of something I see a lot of. Not being open to experimenting. Smart organizations are figuring it out though. The push for a DevOps approach and employing Microservices is a move in the right direction. With DevOps, we can deploy something and if it doesn't work, we can have a different solution out in weeks or maybe months, not quarters or years. With microservices, we get away from the monolithic applications and have a bunch of small, independent components. If one doesn't work quite right, the whole system doesn't fail.

So how open is your organization to experimenting? Are failures discouraged or recognized as the first step towards success? Are you trying to get everything perfect or do you recognize that everything is a prototype, even if it's in production?