Skip to main content

The missing guide to Engineering Processes

Process is important for any startup. But process is a means to an end. It’s never the end product.

I see lots of talented people get bogged down “running a process” and struggling to prioritize and drive what’s really important for their teams. They often lose sight of what really matters, which is Delivering Great Things, As Fast As Is Humanly Possible™.

As managers we put processes and mechanisms in place to enable our teams to do well. But processes alone won’t guarantee success. And too much of it, or too much tweaking of it, can make it hard to remain focused on what really matters.

Great people, with great attitudes, working hard, with urgency and pride in their hearts, guided by “just enough” process will deliver great results.

Time is precious – spend it where it matters

Life is short and opportunities are fleeting. Companies go bust, great teams break up, economic forces change, your own personal circumstances change. Seriously, time is short, don’t waste it on unnecessary process. So if you love what you do, make it your life’s work. Ask yourself, if this is my life’s work, am I proud to say that the work I’m doing now will be my legacy?

If it all ended today, would you be proud of the last few weeks?

If you look back over the last week or two week sprint, think about how you worked, how you hustled, how you learned, how you taught and helped, how you cared and reflect on what you actually achieved. If it all ended today, would you be proud of the last few weeks and hang your career hat on your accomplishments and trajectory?

Then ask yourself the same things but this time about your team. Hopefully, you’re really happy with the answers. I’m pretty happy with mine to be honest. I’m standing tall today.

But if you’re not, why not? What are you going to do about it? What is your team going to do about it? When are you going to start building your legacy, your life’s work, and working and achieving in a way that you’re really proud of? Work that you will be proud to tell your kids and grandkids about, back in the “good old days” before robots took all our jobs. Who’s going to pull you up and get you into this mindset? Wouldn’t it feel better to be able to say you did it yourself? Yes. Yes it would.

Changing your mindset

Stepping down from the soapbox for a second, I’ll share some simple ways you can get started with this mindset.

Firstly, just care about doing a great job. Be open, humble, take personal responsibility for your behaviors and actions and commit to work with people who want to work with you.

If you’re a manager, here are a few more tips…

  • Make sure your team has a meaningful mission, vision, goals and metrics for success. It’s really hard for people to do great things if you haven’t provided them with an inspiring outline of what that looks like.
  • Whatever process you use to “get stuff done” (Scrum, Kanban, Scrumban, Agifall, whatever Frankenstein process the hipsters think they’ve reinvented recently), it probably has some form of a retro and planning meeting. In this meeting, start it with pride. Ask your team: “Of the things we committed to deliver in the last sprint/cycle, which of them are we proud to demo to customers?” Evoke the pride, and use as a tool to inspire, recognize, reward, shame, set the bar. Yes, it’s okay to be ashamed and disappointed in each other sometimes. When the bar is high, it’s natural. If you’re doing it right, the highs will be way more frequent than the lows.
  • Then talk about what else you got done. Did you meet your commitments? Did you hustle? Did you re-scope? Did you really understand what you were doing and what great looked like? Did you care enough? Did you help each other enough? Did you fight for the outcome and each other? Does it hurt if you missed it? Is your pride wounded?
  • After holding each other accountable to doing great work, take a breath and reset. Remember today is day 1, not day 2. You get another chance to be your best next week. Now plan for what comes next. As a team, decide upfront what in particular you want to be “proud” of next time you sit down to do this. Take specific “pride” goals/tasks/items/outcomes/whatever. Pride doesn’t happen by accident. Plan for it, be deliberate.


Popular posts from this blog

On working remote

The last company I worked for, did have an office space, but the code was all on Github, infra on AWS, we tracked issues over Asana and more or less each person had at least one project they could call "their own" (I had a bunch of them ;-)). This worked pretty well. And it gave me a feeling that working remote would not be very different from this. So when we started working on our own startup, we started with working from our homes. It looked great at first. I could now spend more time with Mom and could work at leisure. However, it is not as good as it looks like. At times it just feels you are busy without business, that you had been working, yet didn't achieve much. If you are evaluating working from home and are not sure of how to start, or you already do (then please review and add your views in comments) and feel like you were better off in the office, do read on. Remote work is great. But a physical office is better. So if you can, find yourself a co-working s

Capture and compare stdout in python unit tests

A recent fan of TDD, I set out to write tests for whatever comes my way. And there was one feature where the code would print messages to the console. Now - I had tests written for the API but I could not get my head around ways to capture these messages in my unittests. After some searching and some stroke of genius, here's how I accomplished capturing stdout.

15 minutes of courage

"I Quit" , said she and walked out as briskly as she could, her face as stern as a stone. She didn't look back. I wanted her to. I felt helpless, somewhat creepy, and a sudden chill went down my spine. I didn't know what to do. I wanted to just run away. Run away from her. Run away from this world. Run away to some distant place where I could be myself. Some place where I could cry to my heart's content. But I was not one of those who would leave the ground, wounded! I had always been the one who took life head on. So was it the time to lean back and contemplate what actually went wrong? No. That won't be the man, the world knew! So.. was it the time to build a castle around my feelings and play cold? ~ Prince Mishra