Tag Archives: lean startup

Businesses and Silver Bullets

Posted on by

I’ve been teaching Lean Process Improvement or Six Sigma for about 6 years now. I’m getting into learning Agile in a pretty deep way through reading a ton of books, seeing it in action, and working with Agile teams. I’m currently learning Business Architecture/Enterprise Architecture as well. All of these methodologies are similar but different in some dramatic ways. Lean itself isn’t a project management solution, it has some features of it, but the goal is to take action put something in place and measure the results. Inherently, you’re supposed to be done as soon as possible. Six Sigma has some pretty strong Project management capabilities built into it, but it’s not to be used to install software or some other type of function, it’s design to solve a complex problem, prevent it from happening again and moving on. Agile is totally about managing projects while with as little overhead as possible, while maximizing visibility. This is done through frequent light weight touches and less frequent demos. Finally business architecture is about defining the structure of the business then identifying root causes. I’m the least impressed with Business Architecture at this point because it seems to have the objective of keeping the people at the top in charge while minimizing the amount of empowerment throughout the organization. That’s just my first brush with it though and I could be wrong. The other methodologies are all about empowering the team and the people doing the work so they can be as effective as possible. With Lean and Six Sigma the goal is to eliminate your own job if you’re an instructor or internal consultant, it doesn’t seem the be the case with Business Architecture.

Regardless, all of these methodologies indicate that our businesses are extremely sick. It’s becoming pretty clear to me that the vast majority of current state business practices are flawed and leading to under performing businesses. Lean Six Sigma, makes it clear that there are out dated and poor performing processes. Agile makes it clear that traditional software development doesn’t work and is much too expensive. Business Architecture indicates that no one knows what people are doing, why they are doing it, or where other parts of the organization are doing the same type of work.

In many cases some of the problems looking to be solved by Business Architecture are eliminated in a true Lean organization, but not always. I believe that is why Lean Startup methodology is becoming so popular in both new and old businesses. It’s a novel way to force change in an existing company, while in a Startup it helps keep the company healthy much longer. Furthermore, it forces the company to build effective organization structures early and continually test them.

With the majority of businesses being unhealthy due to out dated processes or aging systems, it’s no wonder why organizations are always looking for a silver bullet. They need a quick fix because nothing is working correctly. The goal to continually drive more and more profits prevents leaders from taking a hard look at what they are doing. Forcing investment in doing the right thing the first time or to do the right thing for the organization even if it takes more time and potentially money.

With my current process improvement classes and engagements I’m seeing a continually struggle between the way you should do Lean, focus on changing what you can, and the reality that most of the work is being done through systems. Even if I wanted to improve processes around the system there’s a limit to what I can do, because I cannot effect change on the underlying system. Changing those systems either IT or organizational can be impossible to do without a strong organizational will and clear strategy. Without either of those, any improvement or agile effort is doomed to fail.

Startups are going to save us, relax everybody

Posted on by

In typical Silicon Valley Breathlessness Forbes published an article by Victor W. Hwang arguing the fact the Startup movement isn’t about startups. He argues that it’s actually a movement to free people from the chains of our current economic system. I definitely don’t buy this. Most people start a company for one of two reasons, they find a problem that they have a better solution for than anything provided (or a novel solution) or to make money. Typically it’s a combination of the two. No company in existence is out there not to make money. Companies that aren’t profitable cannot stay in business for long unless you’re lucky and funded by people that thing you will eventually make them a lot of money.

An opinion piece in the NY Times from 1/2/2014 pretty much sums this fact up. You’re replaceable at a startup and likely even more so than any time in the  future of the company. It’s really easy to fire people when you have no money, especially if you are open and honest about how you go about letting people go.

Furthermore, if the startup movement was in fact about bettering the plight of people we wouldn’t be seeing the social stratification that we’re seeing in cities like San Francisco, ground zero for the startup movement. In SF some of the neo-techno-libertarian-elite are upset that they even see the poor people on their streets rather than out of the way like in cities like NYC (he issued an apology not unlike Tiger Wood’s for being a sex addict). Not only are these the people that are involved in the startup movement, but they are funding it. Yes, I know that this is only one person and on the other side you can point to Alexis Ohanian of Reddit fame, which really is doing a lot of social good.

In some ways the startup movement has made it easier for people to be cogs in the wheel. They work long hard hours, large companies like Facebook and Google push and push to get more for less. In many cases this can cause depression and the exact opposite of what the Startup movement is striving for. In fact, the goal of the Lean Startup is to make it extremely easy to ramp up new employees and ensure full coverage if something goes wrong. These companies and products are designed around the idea of building in quality rather than testing or patching it in. Of course, there’s a benefit to the employee in these cases too – they’re free to really explore new problems and create new things without needing to worry about reoccurring problems.

I do believe there are many startup founders are genuinely trying to change our society for the better, but it hasn’t been a frictionless process and will likely only get worse as we move forward. The Sharing Economy, for example, has come under fire from traditional companies, neighbors, politicians, and even members of the sharing economy. While in other cases, such as Zynga, we see companies that are essentially parasites that thrive through creating addicting games and clogging a platform with their notifications (those notifications stopped and Zynga basically died).

It’s important to be skeptical of statements that glorify any portion of our culture. The article that spurred me to write this has a similar tone as many of Thomas Freeman’s, of the NYTimes, articles, fully optimistic, but missing a broader portion of the population and the long term impact. We should be wary of these articles because we’ll end up believing that it’s more complicated to calculate a median value than an average. The startup movement is to help people start companies, some founders are dreamers, some truly try to change how work is done, but they most aren’t truly changing the world in amazing ways. We’ll be fine if reddit, AirBnB, or some other services vanishes. We were when Digg, Google Reader, Palm and any other influential company vanished.

Lean as a tool for new and mature companies

Posted on by

Today, I finished the book “The Lean Startup” by Eric Ries. Despite the focus on entrepreneurship, I think this book has applications at many levels. First though, I must say that I’ve been using Lean for several years and I walked into this book with an understanding of Lean and how  to apply it at a company. What does Lean mean though? Well, it certainly doesn’t mean cutting staff, reducing the amount of money you have or anything along those lines. It’s a methodology for managing projects, processes and products. It does this by basing decisions on actionable data.

What is actionable data? Well, it’s data that you can do react to quickly if the data is showing trends. This could be a positive trend or a negative trend. If you see something going well and a process is improving over time, (which is abnormal processes typically go out of control over time) then you want to understand how and why it is improving. If it is getting worse over time, you want to understand why and work to improve the process. This isn’t just for machines but also for business processes.

Once you have valid metrics there are several different things you can do. You can simply jump in and try to fix whatever problem is there or you can take a different track. The other track is to do some root cause analysis of the situation. This is called the Five Whys. This is a series of questions that ask Why to understand the real cause of the problem. In one case you may have had a new employee upload something to the production server and it kills the production server. Understanding why might not be as simple as saying, don’t do that again. First you might want to know why the action of the employee took down the server, was it something he did that no one else would have done or was it something else. As you dive down you may realize part of the problem was lack of training but there were issues that would have arisen eventually from someone else. This deeper understanding allows you to make changes at multiple levels rather than installing knee jerk reactions.

That’s a reactionary use of Lean, some other interesting uses of Lean have to deal with experimenting with your product. Ries argues that most companies wait to long to engage customers and put too much effort into the first version of the software. He argues that a company should create a minimum viable product that can be tested to get the basic point across of the end product. Doing this early allows for experimentation with customer feedback. In the software world this is pretty easy to do. You can get to something that early adopters can use and then test changes. As you can route different users to different versions of your website for the product you can have slightly different tests to see what increases the metric that matters. Getting people to continue using your product, but you need to have very targeted metrics to understand what is actually happening with your software. If you use the incorrect metric you will do a lot of work that isn’t driving usage and isn’t driving your revenue.

If you decide to change the way users interact with your GUI, it would be useful to have a goal metric to truly understand if the GUI is an improvement over the previous GUI. This could be tracking the number of clicks it takes to get to an important function. The number of times the user uses your product, the number of times a new user uses the product, but stops using a specific GUI. Once you see your metric moving in the correct direction and you can be sure that it is the result of your changes, then you should end you experiment understand why the users reacted the way they did and try to learn what you should test next.

The early goal is rapid experimentation with purpose and data to back up the decisions you make. These techniques will work with any company, but will also be very successful for a startup.