Personal Thoughts

Elastic Authenticity

Elastic Authenticity

In a recent article, Tanner Wortham talked about the need for unpolished leaders and leadership. In it he listed attributes of unpolished leaders and one of them was –

It’s our leaders’ ability to be true to themselves but also adapts their style to fit the person or circumstance. Let’s call it elastic authenticity.

It made me think about authenticity in a new way. I’ve always tried to amplify my principles in my leadership. And it’s led me to think of it in binary terms.

  • Either I’m authentic, or I’m not.

  • Either I’m principled, or I’m not.

  • Either I’m walking my talk, or I’m not.

  • Either I’m full of S**T, or I’m not.

You get the idea…

But Tanner’s thought made me reconsider my views on authenticity. To begin changing my mental models to be less binary. Instead, take the view that my principles and values as a set of guardrails. Guardrails that allow me some flexibility to be authentic, but not be so entrenched that I feel it’s my way or the highway.

Some things I might start flexing or stretching on include—

Support Systems

Support Systems

Johanna Rothman shared this article and it made me think a bit. Her writing often does that to me ;-) It made me think about two things:

  1. Identifying who my support system is and,

  2. The notion of asking for and giving help.

Upon personal reflection, I realized a couple of uncomfortable truths about myself.

Truth

Truth

I was talking to a fellow agile coach the other day who’s leading her own coaching practice. She’d completed several engagements partnering with two experienced agile coaches and there had been some “rocky exchanges” along the way.

One of the things she said to me that the coaches have given her some really hard feedback of late. Sort of like a firehose of feedback. And that while she appreciated all of it, it was really hard to digest it all. And all of it seemed to be constructive/negative in nature. So, lots to think about and she seemed overwhelmed by it.

I asked her to – look for the truth in it.

And she said something interesting. She said that – it was ALL true.

And I thought for a moment and responded.

No, it’s not all true!

It’s only true from the perspective of the coach’s giving you the feedback. Certainly 100% of what they told you can’t all be true. Nor do you want to take action on all of it.

An Agile Decade: Past, Present, and Future

An Agile Decade: Past, Present, and Future

There have been some troubling trends I’ve seen in the last 10 years of my agile journey. I’d like to share some of them in order to bring them into the light of day.

To be fully transparent, this post was inspired by one that Melissa Perri made here. While the format isn’t the same, it inspired me to look backward in order to look forward.

The lists are in no particular order. That being said, if something made it on the list, I think it’s important!

A (Painful) Look Backward at the Past

Can There be Too Much of a Good Thing?

Can There be Too Much of a Good Thing?

I have a good friend, Ryan Ripley, who is an excellent Scrum trainer with Scrum.org (PST). I just attended a workshop with him and it contained lots of Liberating Structures or LS. 

And when I say lots, I mean LOTS!

And he was clearly excited about them and about stringing structures together. In our debriefs, it was almost as if LS was a pattern language for teaching. In other words, how to teach specific, complex topics and how to communicate to a diverse group of students.

Now I’m not an expert on LS, but it seemed as if Liberating Structures was his new favorite technique when it came to teaching.

But was that good?

Everyone Needs a Coach

Everyone Needs a Coach

The next time you’re looking to engage an agile coach, there’s an additional set of questions I want you to explore with them—

  • Do you (they) have a coach?

  • How often do you (they) meet?

  • What are you (they) currently working on in your journey?

  • What was the last crucial conversation you (they) had with your coach like?

  • Reflecting on your being coached journey, how coachable are you? What are the keys to your being coachable?

What I’m asking you to explore is their personal coaching journey. I feel that most agile coaches are comfortable coaching. But the counterpoint, being coached and being coachable, are often a different question. I guess it’s the age-old challenge of telling being easy and receiving being much harder.

Our Language

Our Language

I delivered a lightning keynote at the StarEast conference in May 2019. If you’re unfamiliar, this format is a 5-minute pitch on any topic you like.

I intentionally went into it without a predetermined talk our slides. I wanted to see what might inspire me before or during the conference. Unfortunately, I waited until the day before the keynote to decide what I would talk about. But I’m sort of glad I did.

My Observation

Mary Thorn and I shared 3 – ½ day workshops at the conference. And during those sessions, and in the hallways, I noticed a trend.

I was listening carefully to people’s questions, the discussions, the stories, and the challenges. And one pattern emerged that caught my attention. The language was very much around –

Did we need a more diverse Agile Manifesto?

Did we need a more diverse Agile Manifesto?

My daughter Rhiannon is a social worker. And I’ve learned from her that my definition of diversity is much shallower than hers. She has a broad, deep, and nuanced view of it and I’m learning to appreciate hers and broaden my own. 

It’s just part of my ongoing efforts to challenge myself and learn.

That being said, it made me think differently the other day when I was reading the Agile Manifesto again. And it dawned on me that –

  • There are 17 signatories to the Manifesto

  • All 17 were men

  • All seemed to be at or approaching middle age at the time (probably well beyond by now)

  • All were white

  • All were software developers with the possible exception of Brian Marick (was he the token tester ;-)

Work Balance Matters

Work Balance Matters

More than a few years ago, I visited a client in Greensboro, NC. I did a little consulting there, but it really wasn’t a longer-term gig.

What stood out to me, after all of these years, is that folks could bring their dogs into work. And everyone seemed to do just that.

  • There were dogs roaming free in the halls.

  • There were dog play areas.

  • There were dogs at their owner’s desks.

  • And those that didn’t have dogs were playing with others dogs.

  • And yes, there was the occasional “doggie accident” ;-)

It was a wonderful environment. Instead of feeling like an office space, it felt like a home that I was visiting. A comfortable home where the family loved their pets.

Another example, kids

What IS your Legacy?

What IS your Legacy?

I spent over 10 years working at a company in Connecticut called Micrognosis. I wrote about an aspect of my experience there in this post.  

During my tenure at Micrognosis we delivered many, many products and projects. We made millions of dollars on our technologies and our customers were fairly happy with our efforts. All of this happened in the span from 1986 – 1996. If you asked me today whether anyone, and I mean anyone, really cares about the efforts we made (products, effort, blood-sweat-tears, etc.), I’d say no.

One of the hidden factors in all of our legacies, and I know technologists don’t want to hear this, is that what we’re working on really doesn’t matter in the long term. No matter what you’re working on!

For example, Netflix or Google or Spotify of today really won’t matter (technically) 20 years from now. Sure, they’ll be historical notes about them on Wikipedia, but the products themselves won’t matter.

SO, WHAT DOES MATTER?