Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

How to Sell Kanban to Your Boss

777 views

Published on

In this webinar, I’ll share my experiences with helping teams communicate the value of Kanban in a way that makes sense to management.

Published in: Business

How to Sell Kanban to Your Boss

  1. 1. How to Sell Kanban to Your Boss.
  2. 2. Hi, I’m Brendan! I have the best job in the world!
  3. 3. Making a business case for Kanban can be tough.
  4. 4. Finance is not math, it is a language.
  5. 5. In my first job as a CTO, I didn’t know the language.
  6. 6. This isn’t uncommon and it causes a lot of problems in business.
  7. 7. To understand how your boss thinks, you must first understand how the CEO thinks!
  8. 8. Stating the Problem.
  9. 9. Clarity We’re not on the same page!
  10. 10. Value We’re not working on the right things!
  11. 11. Unhide The team is a black box!
  12. 12. Focus Simple things take too long to get done!
  13. 13. Ready We don’t get what we ask for!
  14. 14. Trust We don’t keep our commitments!
  15. 15. Done They say they’re finished when they aren’t!
  16. 16. Iteration We don’t finish what we start!
  17. 17. Your boss is “managing up” to someone who sees the problems but can’t offer any solutions.
  18. 18. The corporate world doesn’t value vulnerability — so your boss may receive obtuse mandates like, “Just fix it!”
  19. 19. This kind of environment can make it difficult to sell Kanban practices like “limiting work” and “pull.”
  20. 20. We’ve created a video you can share with your boss that translates Kanban to business value!
  21. 21. Making the Ask ‣ Call a sit-down meeting with your boss. ‣ Tell him or her that you understand they are under a lot of pressure to improve team performance. ‣ Share that you’d like to make a bigger contribution to the team by helping in this area. ‣ Ask if you can setup a time to watch a short video together on increasing revenue by making minor process changes to get their sign-off.
  22. 22. https://vimeo.com/leankit
  23. 23. Bigger Profits with Kanban.
  24. 24. Your team wants permission to “do Kanban.” I’m here to help you make a business case!
  25. 25. Hi, I’m Brendan! I’m a CTO turned trainer. I received same question in 2012. My job has gotten a lot easier with Kanban.
  26. 26. Kanban is a capstone that fits atop your current way of working.
  27. 27. It unhides work, reduces waste, and helps your team improve their flow.
  28. 28. Evolution over transformation.
  29. 29. Kanban is a low risk, inexpensive experiment.
  30. 30. Kanban aligns your team with organizational financial outcomes. Without them knowing it.
  31. 31. 3 Habits
  32. 32. focus
  33. 33. —Greg McKeown “The word priority came into the English language in the 1400s. It stayed singular for the next five hundred years.”
  34. 34. Limit Work in Progress Achieve more by juggling less.
  35. 35. Real Life Example
  36. 36. A team is working on two projects at a time. They deliver both projects every two months, 10 projects annually.
  37. 37. Revenue Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
  38. 38. What would happen to gross revenue if the team worked on only one project at a time?
  39. 39. Revenue Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
  40. 40. Every project would generate revenue one month earlier and one month longer.
  41. 41. An 11th project would be delivered! Gross revenue increase of +12%.
  42. 42. waste reduction
  43. 43. You cannot reduce waste if you are not actively measuring it!
  44. 44. Work can be assigned to everyone and owned by no one.
  45. 45. “Most cars are only in use by their owners for 5% to 10% of the day.” — Elon Musk
  46. 46. Just like cars, work is idle most of the time.
  47. 47. A single communication hack at the team level changed everything!
  48. 48. “I’m finished and I’m waiting for this work to be taken from me.”
  49. 49. Project timelines shrunk from 4 weeks to 3.
  50. 50. Waste reduction delivered a 12th project. Gross revenue increase of +16%.
  51. 51. Flow
  52. 52. Swarming optimizes flow.
  53. 53. Team established policies to speed-up delivery. Card is owned by an absent team member. Card is blocked, stale, or at risk. WIP Limit is not respected. Queue is bottlenecked.
  54. 54. The Impact of Kanban ‣ Realize cashflow earlier. ‣ Increase gross revenue by 16%. ‣ Created capability to deliver two new revenue channels. ‣ Improved quality and customer satisfaction. ‣ Established predictable expectations with business.
  55. 55. Kanban is a low-risk experiment with a massive reward!
  56. 56. Orderly innovation isn’t. Brendan Wovchko training@huge.io http://huge.io/ @hugeio

×