• Tag Archives context
  • Mic check one two, is this thing on?

    Posted on by Tim

    Hello? Can anyone hear me? Is this thing on?

    I was sharing a story with our youngest daughter. She and her older sister are on a speech and debate team at the high school (secondary school) level. She was struggling with a fellow team member to the degree of high frustration.

    It reminded me of how leadership is about influencing others to act or think a certain way.

    I auditioned for in high school (secondary school) and was accepted into both the choir and chamber group. I was one of four or five second-year students to gain entry to the chamber group.

    First, the normal invitation to join the chamber group was as a third-year or fourth-year student.

    Second, the natural progression was from a junior choir to the main choir to the chamber group.

    Finally, based on demonstrated progression, the student received the audition invitation.

    For me, that wasn’t the case. My situation was highly unusual. I played piano and cello in elementary and middle schools (primary school). Occasionally, I sang in the church choir.

    More bluntly, I was accepted into a group based on an audition with zero social credibility and influence.

    Our daughter was feeling a similar lack of credibility and influence. She wanted to throw in the towel, so to speak.

    I threw in the towel, I quit the chamber group and choir in the middle of my third year.

    I regret my choice today as I took the easy way out of social pressure. In sharing that with our daughter it reminded me of how leaders feel at times.

    My senior yearbook photo

    Is this thing on?

    The Navy’s promotion system worked well to provide enlisted leaders with credibility and influence at the senior level. As a chief petty officer, many would be transferred in the weeks and month following their “pinning”.

    Pinning is the event when a Navy member receives the collar devices denoting a new paygrade. Often, this was several months before being paid at the new level.

    When a chief transferred, he or she joined a new command with built-in credibility and influence. To be clear, this action is based on tradition as much as an understanding of familiarity.

    People who are familiar or unfamiliar will treat leaders or new team members as a potential threat until proven otherwise.

    Objectively, our brains are wired this way. We don’t like change. As a result, we get jealous of people who are elevated into authority or who are given greater influence.

    If you can’t get a transfer to a new team, how do you gain credibility and influence?

    For me, it’s about working with positive intent. Expressly, pursue the team relationships with openness and curiosity.

    For this reason, we’ve been given two ears and one mouth. We need to listen with the intent to understand other people.


  • How To Prevent Burnout – Just Say No

    Posted on by Tim

    We must learn to just say no. Europe takes a vacation in August. In the U.S., we don’t take a month off work.

    As people, we need time off to relax, recharge, and reconnect with family and friends.

    Creative work is hard. It demands a lot of energy to stay focused on the goals. As a result, rest is a second thought.

    If one factor tops others, then it is rest. Rest is essential to staying mentally sharp.

    A quick search on rest revealed the following articles:

    If research is indicating rest is important to performance, why, then are we avoiding rest?

    Just say no

    Based on neuroscience, the human brain is wired to seek pleasure. Because dopamine is released into the brain when it encounters enjoyment, behavior becomes pleasure-seeking reinforced.

    In a way, the same thing happens when we connect with people. As well, when we take on and complete projects.

    So, it seems we have wired ourselves for overload. As a result, we’re seeking more dopamine to increase our happiness.

    We resist just saying no as it would stop dopamine from flowing in our brains.

    It’s fair to ask, is burnout worth the dopamine high? Science indicates it isn’t.

    Learn to say no and get some rest. It will do you and those around you good.

    Krk island, Croatia

  • Reflections On Blogging – Year One Complete

    Posted on by Tim

    For me, blogging each weekend nearly one year ago. The action to do it was inspired by my move to Improving. This post covers my reflections on blogging regularly.

    Done is greater than perfect.

    Each blog post on LinkedIn came with risk. In my mind, there are a lot of questions around how posts would be received.

    • First, would people view them?
    • Second, then read them?
    • Third, would people comment on them?
    • Fourth, then share them?
    • Finally, will the posts be valued?

    As a result, I can’t say I’m content. I am focused, like my post on Scrum value #2, but definitely not comfortable.

    Reflections on blogging

    As I write, I become more aware of what I don’t know.

    My new LinkedIn profile banner
    My old LinkedIn profile banner

    By sharing my views, I open myself up to critics. As well, I open myself up to learning.

    Blogging puts me back into the competition instead of sitting in the stands, observing others expressing their own understanding and views.

    Most of my posts don’t go viral. I rarely see more than 1,000 views on LinkedIn. I see even fewer views on this blog.

    That doesn’t stop me from sharing. By failing, I’ve learned what not to do. I’ve learned how to hurt and offend people.

    As a result, I’m not proud of my learning. I am willing to share it to help others act and choose a different path.

    I have a video posted on this blog that speaks to heroes, trauma, and finding “normal”.

    For me, blogging allows me to share the scars I earned in life. To help people understand each other and extend kindness.

    If blogging only positively impacts one person’s life, then my sharing has done what it was intended to do.


  • Scrum Value #3 – Agree Or Disagree, Commit, And Act

    Posted on by Tim

    Part 3 in a 5-part series. This post covers Commitment. Agree or disagree, it doesn’t matter. What does matter is committing.

    The third value;

    People personally commit to achieving the goals of the Scrum Team

    Scrum.org

    One of my former IBM colleagues, says it something like this way.

    “We agree and commit, or we disagree and commit, we just need to commit to action.”

    Mo Shah

    At times, team members fail to personally commit to achieving a state goal. There are many reasons for this. It’s different for each person.

    More frequently, the team fails to set goals. That’s a bit of a “mic drop”.

    Agree or disagree just commit

    Problem-solving is never easy. It is a part of life that is unavoidable. As a result, it takes courage to tackle challenges.

    Gaining team alignment is challenging as well. Defining team goals is worth the effort to avoid friction.

    If there is disagreement about a goal, objective, or outcome then the difference can be worked out.

    A disagreement should not prevent team commitment.

    If Scrum is being properly applied, then changing goals in future Sprints is acceptable to address the disagreement. This goes to the heart of being transparent, inspecting the outcome, and adapting to get a better outcome.

    A wonderful, potential outcome is alignment as work is progressed. The act of moving forward can be a catalyst. As a result, commitment can help in getting past disagreement.

    Value 1, Value 2, Value 3, Value 4, Value 5


  • Agile Principle #7 – Progress Is Things Working Right To Delight

    Posted on by Tim

    Part 7 in a 12-part series. This post covers products and services that are working right to show progress.

    In part six of this series, Blake McMillian wrote about How We Communicate Matters. He explained how communication has changed over just the last few years. Highlighting effectiveness, quality, and richness of communication impacts team outcomes.

    Effective communication influences the theme of this post.

    Working software is the primary measure of progress.

    Principles behind the Agile Manifesto

    In the physical world, it’s hard to get away with manufacturing products or providing services that don’t work. Conversely, building software is a bit different story.

    Maybe it’s because software is intangible in a sense. The intangible nature of software is a post for another day!

    Yet, it doesn’t mean teams don’t build working software. It means that working software is a key measure for teams to assess themselves.

    For a moment, I’ll pick on Microsoft. I upgraded to Windows 11 and understood not all the features or functions would work like Windows 10.

    I didn’t expect my speakerphone to fail along with the “reduced functions” line. To be fair, I had the warning and accepted the risk.

    I’m sure updating plug-and-play drivers are in the backlog, somewhere.

    Things Working Right

    In general, many products and services join the market working right from their introduction to customers.

    But, this is not always the case. Sometimes, products and services are available working somewhat right.

    I recently came across an article about construction updates to Penn Station in New York City. The writer highlights a somewhat right change to the station; $1.6 Billion NYC Train Station Doesn’t Have Enough Seats (msn.com).

    Moynihan Train Hall @ Penn Station, New York City, New York, United States

    Think about the story above the next time your team proposes just releasing a product or service that “might” work or is “somewhat” right. Is it worth the consequences?

    Missed opportunities abound due to avoidable misses. When stuff works right the first time, we all win.

    If a working product or service is the measure of progress, then trying to avoid complicated solutions should be a target. At times, waste is created simply because the solution gets over-engineered from the start.

    Consider this when designing and building the next product or service, regardless of type.

    You can learn more about Agile Principles in Part 8 of this series

    Principle 1, Principle 2, Principle 3, Principle 4, Principle 5, Principle 6, Principle 7, Principle 8, Principle 9, Principle 10, Principle 11, Principle 12


  • Agile Value #3 – See Customers As Allies For Success

    Posted on by Tim

    Part 3 in a 4-part series. This post covers working with customers and clients. Part 1 is posted at this link. Part 2 is posted at this link.

    The third value;

    Customer collaboration over contract negotiation

    Manifesto for Agile Software Development

    Firstly, it is tough working with people.

    Secondly, it is tougher working with customers.

    Thirdly, toughest working with clients and stakeholders.

    Each group has a different investment in the success of a product or service.

    The first group may have a passing interest in the product or service. The second group has an interest in outputs, and maybe outcomes. The third group is the group that cares the most about outcomes.

    Working with customers and clients

    There is a real difference between customers and clients.

    In many cases, customers are “one and done”. They buy the product or service once, twice if it is really good.

    In fewer cases, clients are “repeat business”. They expect the business to protect their interests.

    Internal to the business, are stakeholders. In the absence of customers and/or clients, they serve as representatives.

    Since products and services are being developed for humans, it makes sense to work with the people who use them.

    Have you ever walked through a discount store? Many products that failed in the market find a home in discount racks before getting thrown out.

    Consider the waste created. Enough written.

    Value 1, Value 2, Value 3, Value 4


  • Agile Principle #5 – Motivated People Get The Job Done

    Posted on by Tim

    Part 5 in a 12-part series. This post covers motivated people.

    In part four of this series, Blake McMillian covers Collaboration can Prevent Waste. Rightly, he points out, “Businesspeople and developers must work together daily throughout the project.”

    Consequently, this is key concept teams need to understand. Also, those people need to be motivated in their work.

    Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

    Principles behind the Agile Manifesto

    Work engagement is a challenge today. A Gallup article points to the prior statement.

    “Ways of working” and where work is done have changed. As a result, Principle #5 is more important today than at any time in the past.

    Truly understanding this principle helps teams navigate uncertainty. So, what does that look like?

    Enabling motivated people

    The last part of the Principle is key to granting the first part. It breaks down into three points.

    • “Give them the environment . . . they need”
    • “Give them the support . . . they need”
    • Trust them to get the job done”

    If any one of these three points in bold is missing, then the team suffers. Consider these minimum requirements for motivation.

    What do these, environment, support, trust, look like to a team?

    The list is long and would take forever to fill in this post. However, I consider the following, for me.

    • First, low to moderate pressure (environment)
    • Second, genuine assistance (support)
    • Third, action on feedback (support)
    • Fourth, short, quick status reports (trust)
    • Fifth, fun and engaging (environment)
    • Sixth, open to feedback (trust)

    I’m curious, what is missing from this list? Please add your comments.

    Blake brings us to principle #6, in this post – “How We Communicate Matters“.

    Principle 1, Principle 2, Principle 3, Principle 4, Principle 5, Principle 6, Principle 7, Principle 8, Principle 9, Principle 10, Principle 11, Principle 12


  • Why Balance Between Humanity And Technology Matters

    Posted on by Tim

    For as good as technology is, it should always have a human focus. When we strip away the humanity, we end up losing the vibrancy of the human experience. By adding humanity back into the mix, we restore the balance between humanity and technology in our lives.

    I’m all for reducing the error margin that technology brings into our lives. Additionally, I see how much pain and suffering tech has removed from the lives of many people. My concern is how we are seeing people disconnecting from each other and not having healthy relationships.

    If tech enables a better, richer, more productive human experience, then it should be considered as a positive. If it only serves to damage and hurt people more often than not, then it should be avoided, not encouraged.

    Developing products and services using technology is a worthwhile pursuit. In my mind, much good has happened by continuing to evolve computing and software over the decades since computers were built.

    The Space Shuttle on display at the Air & Space Museumhttps://airandspace.si.edu/udvar-hazy-center

    Finding the balance between

    There is no quick fix to this challenge. Easy answers cover the complexity under the issue.

    To start, look at technology as a tool. It’s not good or bad, just a way to achieve outcomes.

    Secondly, look for ways to test tech’s use:

    • Does this help me be a more effective?
    • Will this help others achieve desired outcomes?
    • Does this waste more time than create more time?
    • Will this improve communication, collaboration, and other human interactions?

    Finally, if question like the ones above are a next positive, then the technology probably is beneficial.

    I challenge you to take a look around. Look hard at your tech use. Be bold and ask yourself and others tough questions.

    If the answers you find disappoint, change your engagement. Because, you own technology, not the other way around.


  • Scrum Value #2 – Focus On The Work Ahead

    Posted on by Tim

    Part 2 in a 5-part series. This post covers Focus. Distractions and busyness slow progress. Being busy is not being productive. Creative teams must focus on the work ahead.

    The second value;

    Everyone focuses on the work of the Sprint and the goals of the Scrum Team

    Scrum.org

    Given the fact that Scrum is an additive framework, processes outside Scrum can be used to help focus the team.

    This means making changes to how teams work. It means creating and maintaining working agreements.

    Restoring focus on the work

    Discovering what improves team focus is important. Unfortunately, the focus is not generally considered a priority action or behavior.

    Here is an example of how refocusing might happen.

    Some companies start applying Scrum with teams that are spread across several projects.

    If transparency is supported, then context switching is revealed. As a result, a choice is on the table for leadership.

    In some cases, that choice leads to having dedicated teams.

    Additionally, fear can cause teams to refocus. It’s not preferred, but it is effective.

    Alternately, making work visible enables focus. Because having the work physically or virtually in front of the team helps improve focus.

    Finally, look for opportunities to help teams focus. As a result, you will be surprised at what you find when you look!

    Value 1, Value 2, Value 3, Value 4, Value 5


  • How Being Pragmatic Helps See The Glass As Half

    Posted on by Tim

    There is beauty in being a recovering perfectionist. Recovery led to a personality shift and the recognition that neither optimism nor pessimism works in for me in life. I landed on being pragmatic.

    pragmatic (adj) – relating to matters of fact or practical affairs often to the exclusion of intellectual or artistic matters: practical as opposed to idealistic (credit Merriam-Webster.com)

    As a child, I saw the world through melancholy glasses and pessimism. For the most part, I was creative and not inclined to practical pursuits.

    At the height of trying to fit in

    That all changed when I enlisted in the U.S. Navy. I slowly shifted away from impractical pursuits to practical matters. I suppose “adulting” and responsibility do that to you.

    Being pragmatic on teams

    Teams evaluate trade-offs. They assess risk and reward for the choices they make. As a result, being pragmatic is important to team effectiveness.

    I appreciate what Dr. John Turner presents on his blog on team science. Specifically on the principles of teamwork.

    A theme I take away from the Team Principles, Category 1 – What is teamwork, is effective teams are pragmatic AND creative.

    No one checks their innate, creative potential when they join a team. Instead, they learn to judge the timing when it’s appropriate to be creative versus practical.

    Like most activities in life, there’s a need to strike balance. This is practical approaches to teamwork can achieve effective outcomes.

    One tools I use to help balance the team dynamics is the Cynefin framework. Cynefin enables problem space identification and team alignment.

    I would encourage you to take a look at Dave Snowden‘s work on Cynefin as its part of my toolbox for teamwork. As well, consider John Turners work on team science to help build understanding about what effective teams look like.