• Hello To Another New Year!

    Posted on by Tim

    Welcome to another new year, 2023! To set the stage for this year’s content, I’ve been planning themes to explore throughout the year.

    First, I’ll cover trust based on Stephen M.R. Covey’s, “The Speed of Trust”. Second, there will be posts on “The Flow System” and its attributes. Third, innovation will be at the forefront of the content this year.

    To avoid confusion, the themes are all related to the purpose of this site. Teams, technology, and training are at the heart of the website. That maybe explicit or implicit, depending on the post.

    I’m excited about what this year’s writing can spark. Trust, flow, and innovation are heady topics. As well, they have great books backing them up, which I’ll reference along the way.

    Each of the concepts have impact teams and training. Also, they are affected by technology in some fashion or form. Unpacking the connects along the path is a worthy challenge.

    New Year Disclaimer

    Bottom line, up front.

    Technology will not make teams better at what they do. It is a tool. It can cause damage when misused.

    With that out of the way, the good news is teams can perform better when tools are used properly.

    There are no spoilers in this post, so don’t get your hopes up!

    Takes some time to review the posts on the Scrum Values. They will help you orient how last year and this year come together in my writing.

    Courage – To Tackle Touch Challenges

    Focus – On The Work Ahead

    Commitment – Agree Or Disagree, Commit, And Act

    Respect – We All Need A Little R-E-S-P-E-C-T

    Openness – Like An Open Book


  • Reflections On A Tremendous Year

    Posted on by Tim

    With so much volatility, uncertainty, complexity, and ambiguity (VUCA) it seems foolish to write, a tremendous year. 2022 was and still is for a few days longer, quite a year.

    I choose to focus on micro, rather than macro, topics for this blog. For me, I could get overwhelmed with the amount of negative news. As a result, I want to inspire the best in you and me with each post.

    For this year, there have been 50 posts made in the blog. Currently, 51 if you count this one as well. I kicked off a series of experimental posts on LinkedIn which help feed longer form content on the blog.

    I have no shortage of natural beauty to take in around our home. We still have fields nearby, which remind me of steady progress in our exurban town.

    My wife and I celebrated 20 years of marriage last month. Our daughters have almost finished high school (secondary school). These are just personal highlights.

    Improving continues to grow with over 1500 Improvers in Canada, Mexico, and the United States. We are strategically adding new firms to the growing concern that align with our values.

    Professionally, the year has been rewarding for me. I’ll spare the details in this post. I will share that after a very challenging 2018 and early 2019, I’ve found a place where I belong.

    A Tremendous Year – Beyond personal

    I set a goal for 2022, and I believe I crushed it. It wasn’t personal, it was altruistic. In a sense, I was climbing Abraham Maslow’s Hierarchy of Needs.

    If you’re not familiar with Maslow’s work, here’s a link – Maslow’s Hierarchy of Needs – Simply Psychology

    Simply put, I wanted to positively impact someone’s life each day throughout the year. A low bar, for some, for me, it was aspirational.

    Measurements are an excellent way to assess impact. So, with that in mind, I capture my LinkedIn numbers and posted them below.

    LinkedIn content performance for 2022

  • Look & Listen – On The Hunt For Weak Signals

    Posted on by Tim

    Weak signals are hard to detect. That’s why they’re call weak signals.

    Are you wondering about the picture?

    Here’s a hint. If you, or someone you know, owns a car, the picture could be a signal.

    I discovered the source of the dots in this picture. It was, <pause for effect> . . .

    An oil leak! Can you believe, our 2010 Toyota Rav4 has an oil leak?

    This image has an empty alt attribute; its file name is 20220719_081944-1024x462.jpg

    It’s not a big leak, but a leak that took me time to recognize. I saw the leak in enough time to avoid significant problems.

    Those spots were my indicator that something was wrong with our car.

    Finding weak signals

    I contacted Ryan, the owner of A Lamp Unto The Streets Auto Repair, to check out the leak. He shared his findings, we talked about the potential cause, and we agreed that I should monitor the situation.

    Are we doing the same with our teams? With the products and services, we provide.

    What weak indicators are people transmitting that we’re missing? How about the market signals we might be missing?

    I’ll grant, there are plenty of distractions and white noise cluttering our world today. We are constantly being bombarded with “urgent” messages that “demand” our attention. The trouble is, we don’t understand the cost of missing the subtle details.

    The challenge is to consider what opportunities are being missed. All it takes is noticing a trend, asking for a solution.


  • Scrum Value #5 – Like An Open Book

    Posted on by Tim

    Part 5 in a 5-part series. This post covers Openness. How much do we know about the work being done? Or better yet, how much do we know about the work not done? These are critical questions that openness seeks to answer.

    The fifth value;

    The Scrum Team and its stakeholders agree to be open about all the work and the challenges with performing the work

    Scrum.org

    Occasionally, I share quotes about being open and transparent from my time in the Navy.

    • “You do not want to be the senior person with a secret.”
    • “Bad news does not get better with age.”

    These quote illustrate how suboptimal outcomes can happen when people are keeping work details held closely.

    There are many reasons for this behavior. Below is a short list of negatives that impact open, candid conversation:

    • Loss
    • Penalty
    • Pushback
    • Ridicule
    • Strife

    A good way to describe this list is a “lack of psychological safety.” I wrote a post about supporting this concept titled, “To Be Creative Nurture And Spark Psychological Safety“.

    Seek openness

    Aside from changes in work culture, open conversations are created by looking at work objectively. Techniques and tools enable conversations that focus on activity rather than personal preference.

    It takes practice to overcome awkward moments during discussion. As a result, showing the work done or to be done is a way to avoid shifting focus.

    In an office, an open wall, adhesive notes, and felt-tipped markers support dialogue. Alternatively, online platforms support remote collaboration and work planning. The three websites below are worth considering:

    • Butter – https://www.butter.us/
    • Mirro – https://miro.com/
    • Mural – https://mural.com/

    Separately, the resources below are helpful for facilitating open conversations.

    In conclusion, openness is essential to getting work done. Additionally, being open helps solve problems that stop work from getting finished.


  • Plunge Into The Flow To Find Insight

    Posted on by Tim

    Getting into the flow is purposeful. My thoughts on the concept of flow are evolving. I’m glad that it is now discussed in the product and service development space.

    The discussion has not achieved clarity. Much like Agile as a philosophy, it has become less clear and more polarized.

    In 2023, I will write a post series covering “Flow”. The series will be like my series on Scrum values and Agile values.

    Consider this as the cinema trailer. “Coming to social media near you and only on www.timdickey.com!”

    Let me be clear, there is a difference between personal and business flow. Personal experience informs business result. Do you want to know why?

    Because people are involved!

    Without people, you can have motion. But then, flow has a different meaning. Recognizing the difference is part of how organizations and individuals can generate a sense of momentum.

    Into the flow by surfing
    Photo by Jeremy Bishop on Unsplash

    Into the flow

    Rather than weigh in on a side of the concept, I’m going to write about tools that enable the flow. For this reason, tools must be used based on context, not preference.

    Context-specific tool use is important as a flow enabler.

    Essentially, misusing tools can cause more harm than good. I present each tool for context-specific employment.

    You might be thinking, “What is context-specific?”

    Simply, you use a tool as designed, not the way you want to.

    My goal is, as we dive into the series, it will cause several responses.

    • First, personal reflection.
    • Second, organizational questions.
    • Third, insightful conversation.

    If the series does not challenge you, then you know more than I do. Given my appetite for learning, I will gladly entertain conversations on this topic.

    I know people who are smarter on this subject, so I expect this journey will be challenging.

    To begin, keep your mind open. Next, come learn alongside me and reason together. Finally, enjoy the discussion we have during 2023.


  • Is Company Culture More Than Words On Walls?

    Posted on by Tim

    Have you ever walked into a business and read the words on walls?

    I read many posts on social media about culture, more specifically work culture. What does that look like?

    For me, at Improving, it looks like the image below.

    In the IT services industry, we support our clients. A challenge is we are working shoulder to shoulder with our clients.

    At times, we might lose focus on what makes us different and unique as service providers. We’re being asked to do challenging work yet stay above some of the messiness our clients are addressing.

    This is where culture becomes critical. As an Improver, I am deeply involved in Improving’s success. I enjoy working with my client, and I do my best to maintain a professional space so that I can serve them.

    Our culture, at Improving, is more than the words on the wall. It is a sense of belonging to a group of outstanding professionals that make us unique.

    Are we perfect? No. Do we fail? From time to time. Do we get better? Yes, hence the name Improving.

    How can companies balance employee desires and business priorities?

    I suggest an answer is in the quote below. Take a minute or two to dwell on the words.

    Work culture is a collection of shared beliefs that the organization seeks to align to. When accounting for each person, it is hard to find alignment on those beliefs.

    Thankfully, Improving has thought through what that looks like for both the business and the people who make it successful.

    Are we perfect in balancing between ourselves and others while showing dedication? My assessment is, we are, more often than not.

    The good news is we can model and show other organizations what that looks like in practice!

    I left the best quote for last. Yeah, time to self-report.

    This is an area where I struggle. I’ve often thought, “You were in the military, you should have this in your DNA by now.”

    No, not so much.

    But I’m practicing being excellent each day. Like writing, this post.

    I cannot become an excellent writer without daily practice—the same with presenting concepts and ideas. If I don’t make a habit of speaking, then I cannot expect excellence.

    At the team level, it’s the same. We ought to be building excellent products and creating excellent services. We create risk we avoid showing our work to each other, our stakeholders, our users, our clients, or our community.

    Risk can then become issues that cause weeks or months of rework. All because we didn’t understand the intent of the people we serve.

    Yeah, I brought teamwork into the conversation here. It’s because teamwork is bigger than a team. It takes a community.

    To be excellent, it starts with you and me. To make it a persistent habit, it resides in the community.

    Do you agree, or am I completely wrong?


  • Technology Triumph – Family, Food, Fun, And Video Games

    Posted on by Tim

    Over the Thanksgiving (US) weekend last year, we drove to a town nearby, McKinney, TX. Each year the town host a “Christmas on the Square” event. It’s a big draw for local business and families alike. What is not to like about family and fun?

    This year was different as the weather did not cooperate. It rained most of the afternoon and into the evening. For me, the conditions were perfect as I don’t like crowds.

    For my wife and daughters, they made the best of a wet situation. By the way, “Christmas on the Square” has become a tradition for my wife and girls, not so much me.

    Since none of the stand and few of the stores were open, it turned into a short experience. Or so I thought. The girls grabbed desert and we started for home after 20 or so minutes in the square.

    As we returned to the parking garage, I asked about a place I knew was open; Arcade 92.

    This looks like fun to me!

    Video games connect family and fun

    Since I had not been to Arcade 92, I only could imagine what I was suggesting we do. Given that our daughters are in the teens, I thought this might be a good way to make memories. Boy, was I right!

    So, this brings me to the heart and purpose of the blog. As well, it brings me to the mission statement for Arcade 92.

    From Arcade 92’s website

    For me, the mission statement ties together my intent for this website. Just like gaming with my kids, my hope for this blog is similar. The wording is just a bit different;

    Bring people together by providing a website to connect through experience

    TimDickey.com’s mission

    Here’s to 2023 and beyond!


  • 3 Critical Thoughts On Design, Indicators, And Quality

    Posted on by Tim

    Design, indicators, and quality are connected. When we don’t think about them, they are doing their job well.

    I was headed into the Dallas Improving office in June. The photo below is what showed up a short distance from home.

    So, indicators and warnings. Yeah, I considered ignoring the tire pressure light.

    But, I didn’t. I drove back home. Checked the pressure. Inflated the tires. Back on the road.

    This brings me to a question on the first of the three thoughts.

    What indicators or warnings are you ignoring from your teams?

    warning light
    Tire pressure warning light

    Building on my thoughts above, I wanted to pose a different question.

    Working in the product development space, I enjoy having a good experience. While the low tire pressure indication might be annoying from time to time, it is important.

    When I consider user experience (UX) and experience design (XD) I want people to note important information.

    Do you appreciate the value of having clear messaging from the products you use?

    Another angle I considered with the original post was quality products or services.

    Simple Theme – Design, Indicators, and Quality

    My car is 14 years old. It has passed the average age for vehicles operating on U.S. roads.

    The story on product quality is the car is still operating well and has very few noticeable defects.

    Since I bought the car used, I don’t know its full history. I can share that for as long as I have owned it (since 2014) it has spent more time on the road than in the repair shop.

    When quality is builtin, products last. Services are relatively easy to access and use. Routine maintenance keeps them operating well.

    What is your experience with quality?

    To tie this together, good design leads to timely indicators and solid quality. When products and services lack good design, they may fail to deliver indicators and quality.


  • Agile Principle #11 – Better Products From Emergence and Self-organization

    Posted on by Tim

    Part 11 in a 12-part series. This post covers how emergence leads to better products.

    Of all the agile principles Blake and I have covered, simplicity is the one I ponder the most. It’s my “most and least favorite”. Why?

    Because of what it suggests in the process of creating products or services. Here’s a good question.

    How do we simplify this release so that it has a value that our client or customer will appreciate?

    The answer lies in the work not done. An outcome of not doing work allows for emergence because there is time to consider the point below:

    The best architectures, requirements, and designs emerge from self-organizing teams.

    Principles behind the Agile Manifesto

    Consider when a painter says, “The canvas compelled me to paint this.” Or a sculpture states, “The rock spoke to me about its ideal form.” In essence, the artist allowed emergence and beauty was created.

    Similarly, products emerge when teams are allowed time to ponder their options. What is notable is the authors mention “self-organizing”.

    In a practical sense, a self-organizing team has experts in different technical and non-technical fields. Emergence can occur when there aren’t external influences or constraints on how the team choose to work.

    Photo by Zoe Schaeffer on Unsplash

    Power of emergence

    For example, when developing software, a business analyst may assist with reviewing a user interface design. Quality assurance testers may work side-by-side with developers. The possible combinations for how a team supports each other are potentially limitless.

    Ideally, the entire team could be engaged in solving the problem at hand. Then they could work in pairs or triplets to bring working pieces together as a solution. The goal is to make sure the pieces fit together to create the whole.

    Additionally, the structures supporting development come from the team instead of being imposed on the team. Architectures and designs flow from requirements as understood by the team working alongside the customer.

    It serves not purpose to work independently of the customer. As well, it is counterproductive to impose structure on teams, as it stifles creative focus.

    To summarize, the people closest to the work learn the right ways to complete the work as it emerges.

    You can learn more about Agile Principles in Part 12 of this series: Reflecting to Improve.

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


  • Powerful Stories – What Do Your Battle Scars Inspire?

    Posted on by Tim

    On LinkedIn, I shared a post about battle scars. In the comments, the discussion took on a novel life.

    One response was related to job search –

    Another response was directly related to the original intent –
    A third response hit on using battle scars for motivation –
    The final response touched on my original intent and scaled to writing books –

    Here’s a link to that post LinkedIn post.

    This link takes you to the YouTube video.

    My battle scars

    I use my experiences, and the scars I have acquired, to help teams be better. Better is subjective. For me, it’s simple. For you, it might be complicated.

    One of my favorite phrases is, “God never wastes a hurt.” It’s the same with experiences.

    A powerful tool I learned while dealing with “survivor guilt” from Afghanistan was reframing. Simply, reframing is looking at an experience differently with an objective lens.

    None of us can change the past. We can choose to remove negative emotions from the experience in the present. Once the negative emotion is removed, we can move toward the future with different expectations.

    I’m not going to lie to you.

    For me, it’s been a long journey to get to the point where I could post about this experience.

    My sense is development teams can benefit from reframing after “creative conflict” or moments of “creative friction”.

    There’s more to unpack in a future post.