One think I do like about the video is that it provides some solid ways to change organizational culture. By providing a solid definition (even if it’s not the one I’d choose), the video is able to specify how to move the needle against that decision:
clarify
embody
celebrate
Determine what behaviors will be rewarded or corrected in your organization, and clarify that to the entire team. Embody those behaviors and live up to them. As someone in my group said with the embody piece, “you get what you tolerate”, so correct or reward the right things. Find the right things to celebrate and do.
I’m sitting in the Leader Development Course from Air University - distance learning. One of the stories I heard this morning has the crux - the commander needs to walk a line between being too involved and not being involved. The story involved the former commander trying to show he cared by being there when new members arrived, by sitting with folks as they did work, and by visiting them when they were out in the field. Later he learned that folks felt like he was checking up on them, making sure they were doing what they were supposed to.
This morning I finished Planet Money’s Episode 963: 13,000 Economists. 1 Question.. These fine folks make one of my favorite podcasts - each week is a different look at something weird from a weird perspective. It sounds like it’s very market/economy focused, but it’s really focused on everything economics. In the past decades economics has branched out to look at nearly every field of human endeavor with a mathematical eye. It’s not always very successful, but the economist perspective does make me look at things differently.
Everybody spends time advocating for something. “Pitching” something. You want your boss to consider a smarter way of working, one that you’ve come up with? You pitch it to her. You want someone to use an open-source project you’ve created? You pitch it to them.
A recent episode of the Freakonomics podcast covered meetings. Two or more people gathering to accomplish the business of business, as they defined it. It gave me some things I hope I remember the next time I’m organizing a recurring staff meeting…
Organize an agenda around questions-to-answer
Hold smaller meetings
Keep track and time
Meetings need agendas, just about every book I’ve read which touches on meetings agrees on this point. The agenda needs to be communicated to participants in advance, so folks can come ready to accomplish it. Folks need to know what to expect. Without an agenda meetings usually devolve into chaos, although sometimes it takes a couple aimless meetings in a row to hit this point. Staff meetings often don’t have a pre-published agenda, but they generally do have a set of topics they proceed through in a set order, and that becomes the known-agenda for the group.
To improve innovation on a team, consider building a team differently based on the problem you’re facing. There are many ways of categorizing a problem your team must solve, but one is along the axis of well-definedness.
Well-defined problems – here, you know what you’re trying to solve, you know what end-state your audience will find acceptable, maybe you’ve seen similar problems solved elsewhere or you even know some current acceptable solutions.
Everybody has a strength. Probably more than one. We are better-employed when we use our strengths. When possible, improving your weaknesses can make you a more effective individual… But we already possess our strengths and can put them to work now.
Build on My Strengths and on My Peoples’ Strengths
Know your peoples’ strengths and put those strengths to work. Build teams with a diversity of strengths. When a task lines up with an individual’s strengths, put them on that task.
When I was flight commander, supervising a group of fellow nerds with nerd jobs, I spent almost all of my time on the administrative requirements. They needed me to do the boss stuff - that was my official position!
I really wanted to do the nerd stuff though. It’s more fun, it’s my strength, and I’ve got more experience with it… I’ll admit that as the boss I had input into many nerdy problems, and having that was rewarding.
I’ve heard this quote numerous times. The falsehood evident in those words should be obvious, but these days perhaps it is not. Reality is reality, perception is perception.
Often reality and perception overlap heavily - but we don’t notice those times when our perceptions are correct. Our brains think that’s the default. There’s also almost always some amount of perception that doesn’t overlap reality - when our brain is jumping to conclusions and we are misled. These situations often don’t matter too much, and sometimes they even keep us safer than we’d be otherwise. Optical illusion is one time when perception doesn’t line up with reality.
I’m personally driven by a few ideas… Things I’m pretty passionate about. Improving cyber security in the US though education is a major one.
When I remember my goals they my action. Why do I want to volunteer to teach at a college? Why did I spend time building K-12 python, cyber security, and boolean logic short courses? Why do I look for opportunities to have my knowledgeable folks teach the rest of my folks?