The last year I've been working with smaller companies because frankly, I was burnt out on big corporate thinking. Multi-million dollar projects go on and on for years with little to show the end user, meetings upon meetings and meetings about meetings. Lots of time and money spent debating company policies, procedures and processes, creating weekly management dashboards with massaged data and pretty colors and filling out templates with information that is almost immediately outdated. In addition to the bureaucracy and the constant stopping to take snapshots of a moving project to assess project health, the solution selected to solve the problem is often a monster to begin with.
Think big or go home. Big companies require big solutions. Step aside, it's enterprise-wide! Gaudy applications with features galore clutter up data centers while most users only use the basic of functionality. Purchased software once featured in CIO magazines sit on shelves while projects are building or buying the same exact type of software. Because a big company's needs are complex and each project infinitely unique.
At big companies that only think big, I've seen simple solutions rejected because they are simple. To suggest such a solution is often met with outrage and appall and quickly dismissed because this person obviously doesn't understand the magnitude of it all. I've seen a newly hired executive suggest a simple solution and as soon as the meeting was over his competence was questioned at water coolers throughout the building.
I find it all very snooty, self-important and wasteful. Over the years, I tried to tell myself that the benefit of such big messes is that more people are working and more parents able to send their kids to college. But I'm not convinced that's how it all works.
Recently to my joy, I read Rework by Jason Fried and David Heinemeier Hansson, the founders of 37 Signals. Here are some of the key points:
- Solve today's problems, not potential ones.
- Build less.
- Fix time and budget. Change/manage scope.
- Be willing to say no to customers.
- Build what you can support.
- Build half a product not a half-assed product.
- Planning is guessing.
To put a little context around the book. It's based on web application development but I really think that the approach can be applied to all technology implementations.
With the economy the way it is, lean thinking is everyone's favorite buzzword. Maybe now big companies will think like start-ups and actually lean businesses. Not holding my breath but I think now I'm ready to go back to corporate gigs and use small company thinking to make big companies better.
