I wrote about treating each other with respect in Organizations Are Not Families, Part 1. In these respect posts, I’ll address possible ways we can treat each other with respect. These are not the only ways. You might have better ideas than I do. Please do comment if you’ve seen alternatives that work better. I […]
I started this series positing that respect is the cornerstone for how we might treat each other, to manage our interactions with success, especially in light of the #MeToo conversation. The series so far is: Organizations Are Not Families, Part 1. Why the metaphor of family-as-org demeans the people working there. Build Respect in Organizations,
I read Joe Berkowitz’s story in Fast Company, John Oliver Was Right: It’s Time To Confront The Dustin Hoffmans In Your Life. There’s a link to a video excerpt in which Hoffman discusses the idea that the people felt like a family. Mr. Berkowitz says this: There is no template for how to be a good
The Case Against Stable Teams, Part 2 In The Case for Stable Teams, Part 1 , I wrote about stable teams as a way to create jelled teams. My guideline was that the longer it took for people to be useful in the team, the more you needed a stable team. Otherwise, the cost of
The Case for Stable Teams, Part 1 A long-time reader, Al, asked me about jelled teams. What makes a team jell? Would I please write an email about that? This is part 1 of 3 part series about teams. Often, a manager forms a new team. The team storms as the people establish themselves and
Own Your Leadership, Part 3 I started this story back in Own Your Leadership, Part 1: Dave and Sherry collaborated to facilitate their team’s ability to deliver one completed feature at a time, to improve the team’s throughput and quality. In Own Your Leadership, Part 2, Sherry realized the team doesn’t have a real PO,
In our first article — “Stay Agile with Discovery” (May 11, 2016)— we discussed how to use a discovery project to show a non-agile customer or sponsor the benefits of going agile. Now we will focus on building trust with a client who is ready to consider agile approaches. After the discovery project, Martha was ready
I published my most recent newsletter, Creating Trustworthy Estimates, this past week. I also noted on Twitter that one person said his estimates created trust in his organization. (He was responding to a #noestimate post that I had retweeted.) Sometimes, estimates do create trust. They provide a comfortable feeling to many people that you have
Creating Trustworthy Estimates Do the people who ask you for estimates trust your estimates? It’s difficult to build trustworthy estimates. Here are three tips you can try for estimates that work for you, not against you. Tip #1: Never provide a single-point estimate. When people ask me for an estimate, I provide a percentage confidence
There’s a twitter discussion of what people “should” do in certain situations. One of the participants believes that people “should” want to learn on their own time and work more than 40 hours per week. I believe in learning. I don’t believe in expecting people to work more than 40 hours/week. My experience is that