An Execution Problem

My biggest takeaway from the TED Conference this week is that we — that is to say, all of us in the world — have an execution problem.  This is a common phrase in business, right?  You’ve done the work of market research, positioning, and strategy and feel good about it.  Perhaps as a bigger company you splurge and hire McKinsey or the like to validate your assumptions or develop some new ones.  And now all you have to do is execute — make it happen.  And yet so many businesses can’t make the right things happen so that it all comes together.  I’d guess, completely unscientifically, that far, far more businesses have execution problems than strategic ones.  Turns out, it’s tough to get things to happen as planned BUT with enough flexibility to change course as needed.  Getting things done is hard.

So what do I mean when I say that humanity has an execution problem?  If nothing else, the intellectual potpourri that is TED showed me this week that we know a lot about the world’s problems, and we don’t lack for vision and data on how to solve them.  A few of the things we heard about this week are the knowledge — and in many cases, even real experiences — about how to:

– Steer the evolution of deadly disease-causing bacteria to make them more benign within a decade

– Build world class urban transportation systems and growth plans to improve urban living and control pollution

– Drive down the cost of critical pharmaceuticals to developing nations by 95%

– Dramatically curb CO2 emissions

We have the knowledge, and yet the problems remain unsolved.  Why is that?  Unlike the organized and controlled and confined boundaries of a company, these kinds of problems are thornier to solve, even if the majority of humans agree they need to be solved.  Whether the roadblock is political, financial, social — or (d) all of the above — we seem to be stuck in a series of execution problems.

The bright spot out of all of this (at least from this week’s discussions) is that, perhaps more than ever before in the history of mankind, many of our most talented leaders AND our wealthiest citizens are taking more of a personal stake in not just defining the problems and solutions, but making them happen.  They’re giving more money, buiding more organizations, and spending more time personally influencing society and telling and showing the stories.  It will take years to see if these efforts can solve our execution problems, but in the meantime, the extraordinary efforts are things we can all be proud of.

It’s a Little Weird When Your Best Customer Experience of the Week is with the Government

Mariquita has been doing a lot of personal admin lately for us.  This week had a little surprise in it.

Verizon continues to be one of the most awful, painful vendors in the history of the universe.
At least their phone network is solid, since any interaction with the people at the company is so bad.  We came to the conclusion this week that they actually do some things which aren’t just the usual bad customer service or outrageous pricing — they have some policies in place that are literally designed to systematically rip off their customers.  The one we ran into was (after 45 minutes on and off hold, of course) that the data plans for Treos are prepaid for a month, but when you go to cancel your data plan, they tell you they HAVE TO cancel it the day you call, even if you have days or weeks left on your plan, and they CAN’T issue a refund for unused days.  But if you complain loudly enough, a supervisor can keep your service active through the end of your pre-pay, or can issue you a refund.  So in fact, they are telling their customer service reps to lie to their customers in the hope that their customers don’t push back so they can keep your money while not delivering your service.

She had a similarly bad experience dealing with our insurance company about car insurance.  State Farm just has a ridiculous set of procedures in place around changing car insurance that cause their customers to jump through hoops several times over for no apparent reason at all.  There have been several stupid things, but this week was needing to take a brand new car to get inspected before insuring it within three days of buying it.  But we had to take it to a specific mechanic on the “approved list” to get it inspected.  That place required an appointment (which meant two trips).  It couldn’t be done at the dealer.  Then the actual inspection lasted about 30 seconds.  Maybe they were just making sure there was an actual car, not a pretend car.  Harry Potter, beware.

And then came the surprise — Mariquita’s trip to the DMV to trade in our old license plates.  She was in and out in under 5 minutes with a prompt, efficient, friendly person handling the transaction with a smile.  Wonders never cease.

It doesn’t take a lot to be great at customer service, just the right mindset and culture.  It’s amazing that Albany (or at least a small pocket therein) seems to have figured that out before some of the biggest companies around.

I read a ton of books.  I usually blog about business books, at least the good ones.  I almost never blog about fiction or non-business/non-fiction books, but I had a good “what did you read this summer” conversation the other night with my CEO Forum, so I thought I’d post super quick snippets about my summer reading list, none of which was business-related.

If you have kids, don’t read Sheryl Sandberg and Adam Grant’s Option B:  Facing Adversity, Building Resilience, and Finding Joy unless you’re prepared to cry or at least be choked up.  A lot.  It is a tough story to read, even if you already know the story.  But it does have a number of VERY good themes and thoughts about what creates resilience (spoiler alert – my favorite key to resilience is having hope) that are wonderful for personal as well as professional lives.

Underground Airlines, by Ben Winters, is a member of a genre I love – alternative historical fiction.  This book is set in contemporary America – except that its version of America never had a Civil War and therefore still has four slave states.  It’s a solid caper in its own right, but it’s a chillingly realistic portrayal of what slavery and slave states would be like today and what America would be like with them.

Hillbilly Elegy, by J.D. Vance, is the story of Appalachia and white working class Americans as told by someone who “escaped” from there and became a marine, then a Yale-educated lawyer.  It explains a lot about the struggles of millions of Americans that are easy for so many of us to ignore or have a cartoonish view of.  It explains, indirectly, a lot about the 2016 presidential election.

Everybody Lies:  Big Data, New Data, and What the Internet Can Tell Us About Who We Really Are, written by Seth Stephens-Davidowitz, was like a cross between Nate Silver’s The Signal and The Noise and Levitt & Dubner’s Freakonomics.  It’s full of interesting factoids derived from internet data.  Probably the most interesting thing about it is how even the most basic data (common search terms) are proving to be great grist for the big data mill.

P.J. O’Rourke’s How the Hell Did This Happen? was a lot like the rest of P.J. O’Rourke’s books, but this time his crusty sarcasm is pointed at the last election in a compilation of articles written at various points during the campaign and after.  It didn’t feel to me as funny as his older books.  But that could also be because the subject was so depressing.  The final chapter was much less funny and much more insightful, not that it provides us with a roadmap out of the mess we’re in.

Sapiens: A Brief History of Humankind, by Noah Harari, is a bit of a rambling history of our species.  It was a good read and lots of interesting nuggets about biology, evolution, and history, though it had a tendency to meander a bit.  It reminded me a bit of various Richard Dawkins books (I blogged a list of them and one related business topic here), so if you’re into that genre, this wouldn’t be bad to pick up…although it’s probably higher level and less scientific than Dawkins if that’s what you’re used to.

Finally, I finished up the fourth book in the massive Robert Caro quadrilogy biography of Lyndon Johnson (full series here).  I have written a couple times over the years about my long-term reading project on American presidential biographies, probably now in its 12th or 13th year.  I’m working my way forward from George Washington, and I usually read a couple on each president, as well as occasional other related books along the way.  I’ve probably read well over 100 meaty tomes as part of this journey, but none as meaty as what must have been 3000+ pages on LBJ.  The good news:  What a fascinating read.  LBJ was probably (with the possible exception of Jefferson) the most complex character to ever hold the office.  Also, I’d say that both Volumes 3 and 4 stand alone as interesting books on their own – Volume 3 as a braoder history of the Senate and Civil Rights; Volume 4 as a slice of time around Kennedy’s assassination and Johnson’s assumption of power.  The bad news:  I got to the end of Vol 4 and realized that there’s a Vol 5 that isn’t even published yet.

That’s it for summer reading…now back to school!

Patience and Impatience are both critical tools in the founder toolbelt. That sounds kind of funny since they’re at odds with each other. Let me explain.

Patience is hard, but there are some things that require it. As they say metaphorically about Product, nine women can’t make a baby in a month. Products needs to be built, tested in the wild, marinate with clients. GTM motions take time to figure out. Brands take time to build unless you have billions to throw at the problem. Bread takes time to rise.  Patience is a really useful tool when people on your team or board get itchy for success and you need to calm them down and keep them focused.

Impatience, on the other hand, is easy, and you have to moderate it. Once we have a vision…don’t we want it to become reality yesterday? Why is that roadmap item taking so damn long? Where’s the blog post? We already agreed to terms on the financing, why do the lawyers need to take 60 days and $50,000 to paper it?

How do you know when to use which tool?

Be patient with the seemingly impossible – changing the world, changing people’s habits, changing thoughts and perceptions all take time. But be impatient with those eminently possible and important items – the things someone on the team or you need to knock off a to do list to advance the business.

Most of all, be impatient for success and tangible signs of progress. Turning your vision into a viable business requires that kind of fire within you.

A Community of Employees

One of the most memorable moments in a valedictorian speech that I’ve heard or read was at my sister-in-law’s graduation from Northwestern about 10 years ago. The speaker’s closing line was something like “Most of all, when you go out into the world, remember to be kind to other people.  It’s one of the best things you can do for the world.”

It’s not as if people are generally trained or predisposed to be UNkind to each other. But respecting other people and being kind to them is sometimes elusive in our busy lives. I think one of the things that makes Return Path more of a community and less of just a “place of work” is this one of our 13 core values:

We are obsessively kind to and respectful of each other

Kindness and respect in the workplace start with the seemingly trivial.  Holding doors open for colleagues, cleaning the coffee machine, helping someone lug a big jug of water and lift it onto the dispenser, and saying a simple “thank you” or “well done” here and there are all acts of kindness and respect. These might seem trivial, but don’t discount the trivial in life.  Being vigilant about the small things sets the right tone for the big things, sort of like the “broken windows” theory of policing says about crime. An atmosphere where people seek out opportunities to help with things like the coffee machine is likely an atmosphere where people seek out opportunities to collaborate on solving problems or cover for a vacationing colleague.

The small things lead to the big things.  We take fit incredibly seriously here.  Fit doesn’t mean that we all have to be the same type of person, or that we all have to like the same kinds of food.  But it means that you have to be kind.  You can be totally frank and direct and challenge authority (more about that in a future post) and still be kind and respectful.  Being a Bull in a China Shop doesn’t work here.

And that’s the difference between a pace to work and a community.

(This is the fourth post in a series documenting the work I did in Colorado on the Governor’s COVID-19 Innovation Response Team – IRT.  Other posts in order are 1, 2, and 3.)

Monday, March 23, Day 7

• Wellness screening – put hot cup of coffee against my temples – now finally the thermometer works (although I can’t say that it gives me a high degree of comfort that I have figured out a workaround!)
• Furious execution and still backlog is growing no matter how much I do – thank goodness team is growing.  Never seen this before – work coming in faster than I can process it, and I am a fast processer. Inbox clean when I go to bed, up to 75 when I wake up, never slows down
• Private sector explosion – this guy can print 3D swabs – but are they compliant?  This guy has an idea for cleansing PPE, this guy can do 3D printing of Ventilator replacement parts, etc.  How to corral?
• Corporate Volunteer form is up – 225 entries in the first 12 hours – WOW
• Congressmen and Senators – people contact them, so they want to help, they want to make news, not coordinated enough with state efforts
• Jay Want – early diagnosis losing sense of smell – low tech way to New Normal
• Coordination continues to be key – multiple cabinet level agencies doing their own thing while multiple private sector groups are doing their own thing (e.g. App – “everyone thinks they’re the only people who have this idea”)
• Mayor of Denver just announced lockdown, I guess that trumps the state solution in town, maybe it’s ok since that just leaves rural areas a bit fuzzier
• Need to revise OS – team is about to go from 3 to 9, private sector spinning up
• Brad OS and State employee OS are different – Slack/Trello/Zoom are not tools state employees are familiar with or can even access.  Now what?
• Kacey insists the team works remotely other than leaders and critical meetings so we can role model social distancing.  GOOD CALL
• One of our private sector guys goes rogue on PR, total bummer – this part (comms) about what we are doing could be more coordinated for sure, but not a priority
• Lots of texts/call with Jared, such a smart and thoughtful guy, really interesting

Tuesday, March 24, Day 8

• Been a week, feels like a month
• Fluid changes to both OS for team and OS for private sector group
• Zoom licenses – state will take a couple weeks to procure them, gotta work around it with Brad
• Slack app won’t get through the firewall.  Maybe IT’s supervisor can do us a favor?
• Comp – interesting expedited process – normally takes 65 days to get approval for temps, today we got it done in an hour!  Comp levels seem incredibly low. But we got done what we needed to get done
• Some minor territorial conflicts with state tech team and our private sector tech team.  Will have to resolve. Surprising how few of these there have been so far given that our team is new and shiny and breaking rules
• Big new Team meeting for first time with Sarah in lead, Red/Yellow/Green check-in (I like that – may have to borrow it!)
• Starting to feel obsolete – love that!  Sarah crushing it, totally feels like the right leader, need to make sure she has enough support (might need an admin?)
• Also…maybe I’m not feeling well?  A little worried I am getting sick. Hope that’s not true, or if it is, hope it’s not the BAD kind of sick.  Going to go work from hotel rest of afternoon
• Call with Jared – concern about managing state’s psychology – testing and isolation services
• Prep for press conference tomorrow

Wednesday, March 25, Day 9

• Woke up feeling awesome – phew – hopefully that was just fatigue or stress induced
• Sarah drowning a bit, feels like me on my 3rd day so makes sense
• Reigning in and organizing private sector seems like a full time job.  We are going to recruit my friend Michelle (ex-RP) to come work with Brad on volunteer management. HALLELUJAH!
• Whiteboard meeting with Kacey holding up her laptop so they can see it on Zoom – hilarious – technology not really working, but we are making the best of it
• State role – facilitate alt supply chain to hospitals since normal chain is broken…also maintain emergency state cache – complex but makes more sense now
• More territorial things starting to pop up with state government…processing volunteers
• Comms overload – here comes the text to alert you to the email to alert you to the phone call
• This team/project is clearly a case of finite resources meets infinite scope and infinite volunteer hand-raising
• Gov press conference – issues Stay at Home order through April 11 (interesting, that wasn’t in the version of the talking points I saw several hours before)
• Meeting some of our new team members.  I can’t even keep up with them, I think we’re up to 15+ now.  Kacey and Kyle are recruiting machines and all these people’s managers are just loaning to us immediately.  Love that.
• Amazingly talented and dedicated state employees – seem young, probably not paid well, but superior to private sector comprables in some ways 
• Talk with Kacey and Sarah about staff/not drowning
• Kacey feels like Sarah is doing a great job, so she cleared me to go home (wouldn’t have gone without her saying ok, she understands how this whole thing is working way better than I do – I guess that’s what a good chief of staff does!)

Stay tuned for more tomorrow…

Book Short:  Which Runs Faster, You or Your Company?

Leading at the Speed of Growth, by Katherine Catlin at the Kauffman Center for Entrepreneurial Leadership is a must read for any entrepreneur or CEO of a growth company.  It’s one of the best books I’ve ever read targeted to that audience – its content is great, its format is a page-turner, and it’s concise and to the point.

The authors take you through three stages of a growth company’s lifestyle (Initial Growth, Rapid Growth, and Continuous Growth) and describe the “how to’s” of the transition into each stage:  how you know it’s coming, how to behave in the new stage, how to leave the old stage behind.

I didn’t realize it when I started reading the book, but Brad had one of the quotes on the back cover that says it all:  “There are business books about starting a company, but they tend to deal with the mechanics of business plans and financing.  Then there are books about ‘how to be the CEO of a Fortune 500 company.’  This is the first book I’ve seen that details the role of the CEO of a small but growing company.”  Thanks to my colleague George Bilbrey for pointing this one out to me.

UPDATE:  Brad corrects me and says that I should mention Jana Matthews, who co-wrote the book with Katherine Catlin and is actually the Kauffman Center person of the duo.

What a View

We’ve done 360-degree reviews for five years now at Return Path.  Rather than the traditional one-way, manager-written performance review, we instituted 360s to give us a “full view” of an employee’s performance.  Reviews are contributed by the person being reviewed (a self assessment), the person’s manager, any of the person’s subordinates, and a handful of peers or other people in the company who work with the person.  They’re done anonymously, and they’re used to craft employees’ development plans for the next 12 months.

The results of 360 are a wonderful management tool.  Mine in particular have always been far more enlightening than the one-way reviews of the past.  The commonality in the feedback from different people is a little bit of what one former manager of mine used to say — when three doctors tell you you’re sick, go lie down.

I know a lot of companies do 360s, but we had two great learnings this year that I thought were worth noting.  First, we automated the process (used to manual in Excel and Word) by using an ASP solution called e360 Reviews from Halogen Software.  It was GREAT.  The tool must have saved us 75% of the administrative time in managing the process, and it made the process of doing the reviews much easier and more convenient as well.  I strongly recommend it.

Second, we started a new tradition of doing Live 360s for the senior staff here.  All people who filled out a review for a senior staff member were invited into an hour-long meeting that was moderated by a great organizational development consultancy we work with, Marc Maltz and Nancy Penner from Triad Consulting.  The purpose of each meeting was to resolve any conflicting comments in the reviews and prioritize strengths as well as development objectives.  We also did a very quick session where the senior staff did “speed reviews” in person of the rest of the company’s leadership team that tried to accomplish similar objectives in a much more compressed time frame and format.

So far (we’re in the middle of them — actually, the team is doing my review as I write this), the results are wonderful.  We’re going to end up producing MUCH crisper and more actionable development plans for our senior staff this year than we ever have in the past.  And the tone of the meetings has been incredibly supportive and constructive.  Having an outside moderator made a huge difference.

And yes, just in case you’re wondering, it is a little bit unnerving to know that a room full of 15 people is discussing you.  Especially when you can hear them all laughing through the wall.  🙂

This is the third post in the series. The first one When to hire your first CPO is here and What does Great Look Like in a CPO is here).

Chief Privacy Officers who aren’t scaling well past the startup stage are the ones who typically have the following characteristics and you should look for some of these telltale signs.

First, if your Chief Privacy Officer looks at you sideways when you ask for a strategy or even a mitigation plan for a breach, then you might have a bigger problem than the fact that you don’t have a plan.  While we like to talk about things like Privacy by Design and using data protection as an offensive strategic weapon, the reality is that Chief Privacy Officers need to have actionable plans in place at all times for the areas where they judge your company to be the most vulnerable.  If you ask to see the plan or get briefed on it and you get back a blank stare, you know you have a reactive person on your hands for what needs to be a thoughtful proactive role.

Second, you might have a Chief Privacy Officer who is not scaling if they would rather lecture you on GDPR than talk about why your data protection plan will win business.  Privacy people can be geeky, legally-oriented, policy-focused and very technical.  All that is well and good but there is so much more that a great Privacy Officer can do. For example, if your Chief Privacy Officer can’t engage in strategy with you and other executives and understand the levers of your business and how their role can help further them, you may as well use an outside law firm instead of taking up a valuable seat at the table internally.

The Privacy team can be small and somewhat insulated from the business, but your Chief Privacy Officer needs to be able to engage the entire company, they need to be thinking strategically about the business, and they need to have short- and long-term plans in place for contingencies and forseeable roadblocks. If they can’t bring these skills to the table at startup scale, how can they bring them to the table when things really take off?

(You can find this post on the Bolster Blog here)

Pret a Manager

My friend James is the GM of the Pret a Manger (a chain of about 250 “everyday luxury” quick service restaurants in the UK and US) at 36th and 5th in Manhattan.  James recently won the President’s Award at Pret for doing an outstanding job opening up a new restaurant.  As part of my ongoing effort to learn and grow as a manager, I thought it would be interesting to spend a day shadowing James and seeing what his operation and management style looked like for a team of two dozen colleagues in a completely different environment than Return Path.  That day was today.  I’ll try to write up the day as combination of observations and learnings applied to our business.  This will be a much longer post than usual.  The title of this post is not a typo – James is “ready to manage.”

1. Team meeting.  The day started at 6:45 a.m. pre-opening with a “team brief” meeting.  The meeting only included half a dozen colleagues who were on hand for the opening, it was a mix of fun and serious, and it ended with three succinct points to remember for the day.  I haven’t done a daily huddle with my team in years, but we do daily stand-ups all across the company in different teams.  The interesting learning, though, is that James leaves the meeting and writes the three points on a whiteboard downstairs near the staff room.  All staff members who come in after the meeting are expected to read the board and internalize the three points (even though they missed the meeting) and are quizzed on them spontaneously during the day.  Key learning:  missing a meeting doesn’t have to mean missing the content of the meeting.

2. Individual 1:1 meeting.  I saw one of these, and it was a mix of a performance review and a development planning session.  It was a little more one-way in communication than ours are, but it did end up having a bunch of back-and-forth.  James’s approach to management is a lot of informal feedback “in the moment,” so this formal check-in contained no surprises for the employee.  The environment was a little challenging for the meeting, since it was in the restaurant (there’s no closed office, and all meetings are done on-site).  The centerpiece of the meeting was a “Start-Stop-Continue” form.  Key learning:  Start-Stop-Continue is a good succinct check-in format.

3. Importance of values.  There were two forms of this that I saw today.  One was a list of 13 key behaviors with an explanation next to each of specific good and bad examples of the behavior.  The behaviors were very clear and were “escalating,” meaning Team Members were expected to practice the first 5-6 of them, Team Leads the first 7-8, Managers the first 10, Head Office staff the first 12, Executives all 13 (roughly).  The second was this “Pret Recipe,” as posted on the public message board (see picture below).  Note – just like our values at Return Path, it all starts with the employee.  One interesting nugget I got from speaking to a relatively new employee who had just joined at the entry level after being recruited from a prominent fast food chain where he had been a store general manager was “Pret really believes this stuff — no lip service.”

I saw the values in action in two different ways.  The first was on the message board, where each element of the Pret Recipe was broken out with a list of supporting documents below it, per the below photo.  Very visual, very clear.

The second was that in James’s team meeting and in his 1:1 meeting, he consistently referenced the behaviors.  Key learning:  having values is great, making them come to life and be relevant for a team day-in, day-out is a lot harder but quite powerful when you get it right.

4. Managing by checklist.  I wrote about this topic a while ago here, but there is nothing like food service retail to demand this kind of attention to detail.  Wow.  They have checklists and standards for everything.  Adherence to standards is what keeps the place humming.  Key learning:  it feels like we have ~1% of the documentation of job processes that Pret does, and I’m thinking that as we get bigger and have people in more and more locations doing the same job, a little more documentation is probably in order to ensure consistency of delivery.

5. Extreme team-based and individual incentive compensation.  Team members start at $9/hour (22% above minimum wage that most competitors offer).  However, any week in which any individual store passes a Mystery Shopper test, the entire staff receives an incremental $2/hour for the whole week.  Any particular employee who is called out for outstanding service during a Mystery Shop receives a $100 bonus, or a $200 bonus if the store also passes the test.  The way the math works out, an entry level employee who gets the maximum bonus earns a 100% bonus for that week.  But the extra $2/hour per team member for a week seemed to be a powerful incentive across the board.  Key learning: team-based incentive comp is something we use here for executives, but maybe it’s worth considering for other teams as well.

6. Integrated systems.  Pret has basically one single software system that runs the whole business from inventory to labor scheduling to finances.  All data flows through it directly from point of sale or via manager single-entry.  All reports are available on demand.  The system is pretty slick.  There doesn’t seem to be much use of side systems and side spreadsheets, though I’m sure there are some.  Key learning: there’s a lot to be said for having a little more information standardized across the business, though the flip side is that this system is a single point of failure and also much less flexible than what we have.

7. Think time.  I’ve written a little about working “on the business, not in the business,” or what I call OTB time, once before, and I have another post queued up for later this summer about the same.  Brad Feld also very kindly wrote about it in reference to Return Path last week.  Working in retail means that time to work on IMPORTANT BUT NOT URGENT issues is extremely hard to come by and fragmented.  I suspect that it comes more at the end of the day for James, and it probably comes a lot more when he doesn’t have someone like me observing him and asking him questions.  But his “office” (below), exposed to the loud music and sounds and smells of the kitchen, certainly doesn’t lend itself to think time!  Key learning:  of course customers come first, but boy is it critical to make space to work OTB, not just ITB.  Oh, and James needs a new chair that’s more ergonomically compatible with his high countertop desk.

Years ago, I spent a few weekends working in my cousin Michael’s wine store in Hudson, NY, and I wrote up the experience in two different posts on this blog, the first one about the similarities between running a 2-person company and a 200-person company, and the second one about how in a small business, you have to wear one of every kind of hat there is.  My conclusion then was that there are more similarities than differences when it comes to running businesses of different types.  My conclusion from today is exactly the same, though the focus on management made for a very different experience.

Thanks to James, Gustavo, Orlanda, Shawona, and the rest of the team at the 36th & 5th Pret for putting up with the distraction of me for the bulk of the day today — I learned a lot (and particularly enjoyed the NYC Meatball Hot Wrap) and now have to figure out how to return the favor to you!

Ratcheting Up Is Hard To Do (or Boiling the Frog, Part II)

I’ve had to ratchet down business several times over the years at Return Path.  Times were tough, revenues weren’t coming as fast as promised, my investors and I were growing weary, the dot com crash, etc. etc.  We had layoffs, consolidated jobs, cut salaries multiple times, made people wear 8 hats to get the job done.  It’s an awful process to go through.

In the last year or so, business has finally started going much better.  We’ve been fortunate in many ways that we’re still around, with products that work really well, with a good customer base, and with good and patient investors and employees, as the business climate has improved.  We’ve grown from 22 people (at our low point) up to almost 75.  But what that has meant for our organization is that we’ve had to quickly "ratchet back up," adding people, adding new functions that were previously one of many hats worn by a single person, operating at a different level.  While ratcheting down is a nightmare, it turns out that quickly ratcheting back up is in many ways just as hard on the organization.

Some examples:

– IT (internal email and servers) has been run by a part-time resource and "off the side of the desk" of our product development engineering department.  Now it is almost completely broken, and it turned out we hired a very talented IT manager, probably about three months too late.

– Staffing up is particularly tough without a dedicated HR function and with a legacy of missed budgets.  HR has been done off the side of the desk of me and my executive assistant, and we can’t keep pace any more with all the recruiting, hiring, training, and development planning.  Now that we feel like we need and can afford more staff, we need to hire an HR manager to handle it all, but we need someone in place and trained today, not three months from now.

– A 22 person company can function brilliantly as a network of Individual Contributors who loosely coordinate with each other.  But now what we need at 75 is a a few hardcore Managers that can build systems and processes so that the whole machine runs smoothly.  We don’t necessarily have those people in-house, and if we bring them in from the outside, I’m left wondering if the Individual Contributors will feel like their years of hard work aren’t appreciated if there’s a new layer of management surrounding them.

I hope we never have to ratchet down again…but part of the reason why now is that I never want to have to ratchet back up, either!

Thanks to my COO and business partner Jack Sinclair for his help with this posting.