I took a brief break from writing about software to write about cardboard creations (there will be more), but now I’ll come back to writing about software. Specifically, I want to talk about the small team and how to actually get things done. Continue reading “Getting Things Done With A Small Team”
Category: Leadership
Lean and the Team
In my last post, I talked about comparative advantage and how it can aid you in developing your team and your members’ skills. Now, I’ll talk about another aspect that you need to consider in a lesson from Lean.
I have never described myself as a person who espouses any one single methodology for solving problems, so you won’t ever see me write about the one right way of doing things. Many processes and frameworks were originally designed for one thing, and I have had uneven results applying them to software development. One thing that I have found to be very helpful in developing a team is a specific subset of the Lean concept of muda, which I came to understand when reading the book The Goal.
If you haven’t read this book, it’s highly regarded and a bestseller for making certain business concepts very accessible to the reader. I highly recommend it.
The book has two great takeaways – first is the answer to the question: What is the goal of a company? The answer: To Make Money. It’s a very handy thing to keep in mind.
The second takeaway is the Theory of Constraints. This is the idea that production bottlenecks can take an assembly line and slow it to the speed of its slowest machine. Continue reading “Lean and the Team”
Ricardo – Team Economics
My previous post was about starting out with a small team, and some ideas on leading it. The next few posts will talk about a few useful tools that I use in developing and shaping a team.
I didn’t do well in either macro or micro-economics in college. I was working my way through the liberal arts to find out what I was good at, and it turned out not to be econ. In college, however, I always enjoyed reading P.J. O’Rourke’s books. I was too young to see the cynicism, and so I read pretty much everything he wrote for several years, laughing out loud all the way. It wasn’t until I read Eat The Rich that I finally found one thing in economics that I can use practically daily: Ricardo’s Theory of Comparative Advantage. Now, I can’t do O’Rourke’s writing on this justice (Eat The Rich, Page 104-123), and I highly recommend reading it (along with all his books published before around 2000 – I haven’t read any since then), but I think it’s useful to discuss. Continue reading “Ricardo – Team Economics”
The Small Team
In my last post, I wrote about the choice between specialists and generalists on a team, using the metaphor of role-playing games to illustrate it. Now, I’m going to write a bit, over the next few posts, about my practical experience building and growing teams. This isn’t meant to be a guidebook on team development, or anything, but more of my approach and philosophy on team building.
Sure, I also happen to have another awesome picture for this post that I feel reinforces my credentials in Role Playing Games, but that’s a total coincidence, I swear. Yes, I do just have these books lying around my office.
At many jobs I’ve had leading teams, I’ve started with somewhat small teams. For illustration purposes, the team I’ll describe will be an example, and not really any particular team I’ve actually had. Continue reading “The Small Team”
Pity the Wizard
At times, I’ve felt the temptation to equate the development and growth of a team to that of a party in a Role Playing Game. But, while the RPG analogy does have some striking resemblances to real life, it is better for telling us about pitfalls than about actual good practices. They are both similar in that you start out a Role Playing Game with little knowledge of your task, and build a party based on intuition. As the game progresses, you realize that your party design is not exactly aligned to the tasks that you are confronted with. Continue reading “Pity the Wizard”