crushing pressure

Should Temperance be A Higher-Valued Leadership Quality?

As a Co-founder at Event Espresso and Event Smart, I function in many roles: project management, sales rep, technical support, accountant, marketer, counselor, etc. I’m faced with handling challenges from just about any area. This is where my formal education has come in very useful, by the way. Too, I am rarely fully informed about a situation and I often have more questions than answers. However, I often struggle with determining whether something needs my attention or not, now or later, whether my team is being distracted or mislead and how I lead our team through the situation. It’s not an easy task to be clear and level-headed, and the way I engage (or not) in a situation influences my team.

I enjoy road cycling, and am motivated to ride harder by the beat of Eminem’s song Toy Soldiers. More importantly though, I often ponder some of the [clean] lyrics:

I’m supposed to be the soldier who never blows his composure
Even though I hold the weight of the whole world on my shoulders
I ain’t never supposed to show it, my crew ain’t supposed to know it
Even if it means goin’ toe to toe with a ______ it don’t matter
I’d never drag them in battles that I can handle unless I absolutely have to
I’m supposed to set an example
I need to be the leader, my crew looks for me to guide ’em
If some ____ ever does pop off, I’m supposed to be beside ’em…

While Eminem intended to communicate his own expectations as a leader, I feel he adequately conveys my expectations for myself in my role professionally. I should also feel this responsibility in other areas of my life too, like at home.

I believe a certain level of transparency is good, but leaders also have a special responsibility to bridle our emotions that can affect others in a negative way. Our emotions can lead us and our team to over-emphasize details or over-react to situations that can influence us to focus on the wrong things and make the wrong decisions.

To help me be the leader I want to be, I have a sticky note on my monitor that reads: “Do I need to react? How should I respond?”

That message helps remind me to more deliberately decide whether I need to react to a situation and how to do so. If I do decide to engage, the second sentence encourages me to pause just a second to think about how I should get involved. I can’t fault my team for how they feel about a situation, but do I contribute in a positive or negative way? Do I clarify the situation? Do I calm the situation? Or do I add fuel and confusion to the fire?

It is rare when we immediately and completely understand a situation. Instead, we usually comprehend a situation gradually over a period of time. The challenge for us is to recognize when we are fully informed or lack the understanding to make a decision at all. Once we are more self-aware we can better understand the context and respond.

In software development you are faced with a nearly infinite number of possibilities, scenarios, conditions. So one of the challenges is determining what to actually worry about, what to be motivated by, and when to act. Are you scared and do you freak out every time your competition releases a new product or secures a big client? Are you debilitated with each bug in your program or when someone leaves your team? Do you need your team to react like you, and are your emotions rubbing off on them, or are they allowed to respond differently?

We can’t be so naive to think our emotions don’t matter. Some people will absorb emotions more readily, while other people will be more temperate. Whatever your decision making process, as a leader make sure that you are intentionally and skillfully applying the right positive pressure to encourage focus, or reduce pressure to diffuse a situation.

This doesn’t mean you can’t get emotional, rather it means you have to use emotion with skill and responsibility.

When have leaders in your life shown temperance or the lack thereof?

Lastly, are you a leader? Aren’t we all leaders, in our jobs, at home, school, church, on even on the road? And if you think you are not a leader, you underestimate yourself.

remote controls commercials and team cadence

What I Learned about Team Cadence When My Wife Had the Remote Control

If you’re a sports fan with DVR, you usually have a queue of recorded sporting events to catch up on before you accidentally come across the scores in the ticker tape, headlines, get a score notification on your mobile device, or a text from a friend ruining the surprise. 😖 And, if you’re going to get through that queue of excitement quickly but without missing the action, you have to be skilled with a remote control to skip the commercials and intermissions.

There is Skill to Using a Remote Control

I have mastered just such a skill.  I have a sense of knowing when to start and how long to 4xfast-forward (>>>>) the recording before I need to push the play button again just as the commercials end and the sporting event resumes. I have the muscle memory for knowing how many taps of the fast-forward button and how long to let it fast-forward before pushing the play button. This muscle memory has developed because the commercial breaks are predictable enough that I can almost anticipate when they start and stop.

It wasn’t until I let my wife hold the remote and be responsible for skipping the commercials did I realize that she was still learning the higher ways of using the remote control. She didn’t fast forward right at the beginning of a commercial break, so we were stuck watching lame commercials for a while. Then, sometimes she fast forwarded too much and we missed part of the game when it came back on. If you’re Type A like I am, it is a little painful to refrain from taking over. 😱

Are You That Familiar with Your Team’s Cadence?

Because of enough experience with television programming, commercials, and the remote control, I can skip commercials with ease. I also have a sense for my team’s cadence of accomplishing tasks. Do you have a sense for how fast your team is moving? Does your team have a rhythm, a fairly consistent burn down rate or velocity? Would you notice when things change? I did.

We have a new project that is running over time and over budget. This new project has been particularly challenging because it has required a new development skill-set, new tools and new service. It’s an important project, but our approach has taken us out of our normal expertise. We had a chance to re-evaluate that project and decided to slow down development on that project and re-focus on our core projects.

Within two days of redirecting our development toward the tasks that we normally work on, I noticed we were completing the development we are more familiar with at a much faster pace and more predictable rate (cadence).

I also noticed a change in the demeanor of those affected. We had added motivation and energy because we were able to get things done.

When I have the remote, we watch fewer commercials and more sports. When my wife has the remote, we watch more commercials and less sports. Likewise, when your team is taking on tasks that they are not familiar with doing, you will get less accomplished and perhaps be frustrated.

My Wife Helped Me Connect the Remote Control and Team Cadence

I’m not throwing my wife under the bus. She is amazing. ❤️ She just wasn’t doing what she does best (baking cinnamon rolls is where she really excels). She was actually trying to help me relax and watch games while my hands were full typing blog posts. But then she also taught me something:

If your burn down rate or development velocity is not what it normally is, then you might reconsider whether what you are doing now is what you are best at doing.

counting priorities

3 Factors to Quickly Set Short-term Development Priorities

There are an unlimited number of factors you could take into consideration when determining what projects or tasks should be a priority. You will likely use different factors when considering long or short term priorities too. What factors you actually use will be a reflection of the mission of your organization. Recently I spent a little time setting priorities for our Event Espresso and Event Smart developers for the next week. During this process I used Speed, Impact and Strategy to make the process of setting short-term priorities more practical. 🔨

Most Factors Distill Down to the Mission of the Organization

If the organization has a mission to make money, the organization will focus on what will drive money now and later. If the organization is focused on a different specific purpose, then the purpose of the day will be whatever can forward that mission.

Sometimes the “Mission” is Too Ambiguous to be Helpful

However, sometimes using the mission of the organization is not clear enough for the day-to-day decision making to be very helpful.

Here is a mission statement for Coca Cola that is probably less than helpful for a manager or programmer to decide what software code to work on today.

The Coca Cola Company Mission. Our mission is: To refresh the world in mind, body and spirit. To inspire moments of optimism and happiness through our brands and actions.

If you’re a programmer could you justify doing yoga to support that mission statement? 🤔

And if you’re the manager of that programmer, you won’t be very happy with the progress of your software project at the end of the week.

We have a mission statement and vision for Event Espresso, but that’s not necessarily enough to tell us what we should work on today, tomorrow or next week. For the real short-term planning I favor: speed, impact, and strategy.


Speed is important because sometimes a developer can complete a task (or several tasks) that can collectively improve a customer’s experience. Sometimes a few quick wins can increase your team’s morale, momentum and energy.

Getting a batch of issues resolved quickly can also clarify the fewer remaining tasks.

Even if a task has a lot of impact (discussed next), it might take a long time to get done, which can delay other enhancements.

So, the speed or velocity of completing the tasks is important. The faster a developer or development team can get something done the more likely it will be a priority today.


Some of the tasks you might consider will be trivial or significant. In the short-run, I favor projects that can have the biggest impact in the shortest amount of time. We often categorize tasks by the amount of work we expect it will take. So when we are evaluating a task we can get a sense that if we invest a little in that task it will be done pretty quickly. That gives us confidence that we can make customers happy and increase our chances of gaining market share in the event registration and ticketing software space.


Even if there are features or bug fixes that customers want addressed, and we can do that task quickly, that still doesn’t mean those tasks should be a priority. In the software business you want to avoid throwing every little suggestion into your program. Unnecessary features and code creates technical debt that will have to be maintained and will impact future development (for good or bad). So, only when a task fits into the purpose of your software should you consider investing resources into that code.

What factors do you consider?

There are a lot of other great factors that could also be considered, such as marketability, popularity, etc… but I’ve discussed just a few of the more easily understood factors I use to help set development priorities in the short-term.

Give some encouragement and share a little…What factors do you use to quickly set short-term priorities? If you haven’t thought about it specifically, pause for a minute then tell me what you think.