Tag: management

  • Mastering New Leadership Styles

    Credit: Wikimedia

    “The best leaders master multiple leadership styles”, blithely comments some post on leadership. OK, including one written by me. But how? Many leaders are overly reliant on a style and this can hold them back. Generally leadership styles are a function of emotional intelligence, and working on emotional intelligence, such as working on becoming more coachable may help, but how to work on this aspect specifically?

    That depends on the style you want to build out. In 2000, Daniel Goleman published research in the Harvard Business Review identifying six main styles of leadership, each originating from different aspects of emotional intelligence—Pacesetting, Authoritative, Affiliative, Coaching, Coercive and Democratic. Even though our expectations of the workplace and of our managers have changed in that time, these styles are still a useful place to start in considering what situations call for and the styles we tend to default to ourselves.

    Pacesetting

    Pacesetting leaders expect excellence and self-direction.  A leader who sets high performance standards and exemplifies them himself has a very positive impact on employees who are self-motivated and highly competent. But other employees tend to feel overwhelmed by such a leader’s demands for excellence—and to resent his tendency to take over a situation.

    When is it useful?

    Pacesetting is for those times where there’s just a lot to be done. Maybe you’re digging out a backlog, or surviving an intense period. Direction should be very clear, with minimal need for collaboration or experimentation.

    What do you need?

    Stamina and focus. The pacesetting leader is rarely known for their work life balance. You need to be ruthless in saying no to the things that are not core to your effectiveness.

    Situations to seek out?

    Look for the numerically measurable problem, where everything is fixable by just Doing The Work. Just make sure it’s not indefinite, and that you have what you need to be successful.

    Shift your mindset

    High expectations of other people are key to the pacesetting leadership style, and what distinguishes the pacesetter from the general hard working leader. Most of the hardest working leaders know they cannot expect the same level of dedication from their teammates – their commitment and work ethic are often what has propelled them up the ladder. However to be a pacesetting leader, you need to demand excellence from your teammates, which means you need to have a clear idea of what excellence is, and be prepared to set expectations accordingly. Some people may match the style without you saying anything; others may have to be told.

    I suspect one of the reasons why pacesetting has a negative affect on teams is that pacesetters over rely on working harder and miss the point where they need to work smarter instead. Make sure that you deploy this style when working harder will make the difference – and switch to another style when it won’t. 

    Authoritative

    Authoritative leaders mobilize people towards a vision. An authoritative leader takes a “Come with me” approach: she states the overall goal but gives people the freedom to choose their own means of achieving it. This style works especially well when a business is adrift. It is less effective when the leader is working with a team of experts who are more experienced than he is.

    When is it useful?

    Authoritative is helpful when you have a new, or lost team, that needs a way forward. 

    What do you need?

    Well-founded confidence in the domain and your own expertise, the ability to tell a compelling story about what the team is doing and why. 

    Situations to seek out?

    Seek out a problem where you have a strong reputation and deep expertise. Potentially a slight adjustment or repeat of something you have done before. This might seem a little dull – who wants to do the same thing again? – but will allow you to be more definitive and work more quickly.

    Shift your mindset

    The differentiator of the authoritative leaders is confidence. They believe they know the way, and they will lay out the path to get there. To take on this style, you need to believe that you know how to address the situation. This doesn’t mean not listening to other people, but it does mean fitting that information into your model and pushing things forward. This style is best adopted when it comes based on a reputation earned elsewhere, ideally nearby, so you need to be able to take pride and believe in your past accomplishments, too.

    Affiliative

    Affiliative leaders create emotional bonds and harmony. The hallmark of the affiliative leader is a “People come first” attitude. This style is particularly useful for building team harmony or increasing morale. But its exclusive focus on praise can allow poor performance to go uncorrected. Also, affiliative leaders rarely offer advice, which often leaves employees in a quandary.

    When is it useful?

    This style is incredibly useful when healing a broken team, or bringing together a team exhausted (perhaps by the pacesetting style…).

    What do you need?

    Patience and empathy. You need to be willing to hear people out, give people space, and let some amount of chaos happen as the team evolves. 

    Situations to seek out?

    Look for the team you believe in, that you can see has had a hard time as a result of outside forces. Maybe you take over from a bad leader, or at the end of a difficult time (e.g. a team that has been scaling).

    Shift your mindset

    Affiliative leaders believe that the responsibility for team health and culture lies with leadership. It means taking a deep and personal responsibility for the culture of the team, and working to create an environment where everyone can be successful. You will need to rank team goals after team health (and have the space to do so).

    Coaching

    Coaching leaders develop people for the future. This style focuses more on personal development than on immediate work-related tasks. It works well when employees are already aware of their weaknesses and want to improve, but not when they are resistant to changing their ways.

    When is it useful?

    This style is useful when there’s been a lack of personal development, for example people haven’t been getting feedback, or when stretch assignments come without support. It can unlock a huge amount of capacity in your team or organization. 

    What do you need?

    Patience and optimism.

    Situations to seek out?

    Look for situations where people haven’t been set up to succeed, but who have done okay under the circumstances. For instance, people who were reporting to someone who didn’t make time for them. Pay attention to how coachable they are, and how they view team responsibilities.

    Shift your mindset

    Coaching leaders believe in each individual. Shifting to this style means shifting your mindset and evaluating each individual on the team not against your expectations, but against their best selves. Coaching leaders are a buffer who believe more in people who don’t believe in themselves; this creates a balance against those who tend to over-confidence (and failing upwards).

    Coercive

    Coercive leaders demand immediate compliance. This “Do what I say” approach can be very effective in a turnaround situation, a natural disaster, or when working with problem employees. But in most situations, coercive leadership inhibits the organization’s flexibility and dampens employees’ motivation.

    When is it useful?

    As much as we don’t like to admit it, at times, as leaders, our job is to tell people what to do. People who embrace this style do it too much, but we all need to be willing to use it at times.

    What do you need?

    Conviction.

    Situations to seek out?

    Moments where you know you are right and someone else is wrong, and it’s your job to tell them so.

    Shift your mindset

    Dig into that righteous anger and channel it, even if you don’t express it fully. Personally, I am never more icily British than when I am consumed with rage; the last time I deployed this style the conversation started, “A note on etiquette…”

    Democratic

    Democratic leaders build consensus through participation. This style’s impact on organizational climate is not as high as you might imagine. By giving workers a voice in decisions, democratic leaders build organizational flexibility and responsibility and help generate fresh ideas. But sometimes the price is endless meetings and confused employees who feel leaderless.

    When is it useful?

    There’s a reason why most new leaders start with around 90 days of listening; this style is incredibly useful for a new leader building credibility in a new organization, as it ensures that everyone feels heard and maximizes buy in. This style can be useful even when you are confident you have a good idea of what’s going on, as you can diffuse resentment by showing you are listening and making people feel heard.

    What do you need?

    Patience. The leeway to invest time up front in exchange for increased buy in later.

    Situations to seek out?

    Seek out situations where you know what you don’t know, and where building the knowledge to be effective is part of your remit so you’ll be given the time to do so.

    Shift your mindset

    The mindset of the democratic leader is we will make better decisions together. They would sooner have the “best” 100% result of the collective than the 80% the individual might create alone. They are willing to prioritize that buy in, consistently, even when there are pressures that might make a more expedient solution more appealing.

    Where to Begin?

    It helps to start with the end in mind. The goal is some level of comfort with all of these styles, even if you tend to use some of them very sparingly.

    The easiest way may be to build around, starting with what you’re comfortable with. If you default to affiliative (as many new managers do), start adding the democratic style and making sure that decisions are made. Work on getting better at coaching people. These three styles are incredibly compatible with each other, and mastering them alone will take you a long way. Eventually, though, you will need to branch out.

    If you need to make a more extreme change, either because you are reaching the limits of your effectiveness or in response to feedback, it may be harder.

    If you fall on the “softer” side – affiliative, democratic, coaching – seek out or embrace a situation where combining the authoritative and pacesetting styles is warranted. It should be relatively timeboxed, so know that once you’re out the other side your other leadership strengths will allow you to deepen and continue your impact. Make sure that you have (well-founded) confidence, and the support you need to be effective, like a coach and supportive friends to get real with, because you’ll need to continually project that confidence to the team, even if you don’t always feel it yourself.

    If you fall on the “harder” side – coercive, pacesetting – try embracing the democratic or coaching styles more actively (they are less emotional than the affiliative style). Find some people whose potential you believe in and work on developing them, seek out situations where you have influence rather than authority and lean into it, for example working across the org. You’ll have to take a deep breath and accept that progress won’t happen on the timeframe you think it should, but then… did it ever, anyway?

  • How to build—and manage—a self-improving team

    My latest in Quartz…

    A lot of things in management become clearer when you realize it’s much easier to measure a team’s progress than its state.

    A team produces 30 units of “x” in a week. Is this good? Well, we could start by asking what the value of each unit is, or by looking at the contributions of each individual on the team…

    Or, we could look at how many units are being produced over time, and whether delivery is getting more (or less) predictable. This will tell us more about the trajectory the group is on. Is the team gelling, working together better, delivering more? Or are members of the team struggling, maybe with a lack of clarity about their mandate, or because they are onboarding new people without the right process in place to support that?

    There’s a concept of “self-managing teams,” which I prefer to reframe as “self-improving teams.” Self-improving teams have feedback loops that make getting better over time a team effort; they respond well to failure and learn as much from it as possible, they use estimation as a way to better surface the known—and unknown—unknowns. They invest in collaboration that levels up individuals and the collective.

    The question that might emerge from this is, well, if your team does all this on its own, what is the role of the manager? Doesn’t it render you redundant?

    Continue reading…

  • Why a good boss likes it when people complain

    My latest in Quartz…

    I know some managers say “don’t bring me problems, bring me solutions,” but personally I don’t subscribe to it.

    I love when people complain to me. Of course, complaining is a national past time for the British, and we don’t just limit ourselves to complaining about the weather, or the poor availability of good tea when traveling. Brexit has provided some strong fodder for complaining (where do we begin?) but really your average British can complain about anything.

    But, here’s why complaining is so useful to me as a manager.

    Continue reading…

  • As a leader, your job should change every six months even if you stay put

    My latest in Quartz…

    Leadership roles evolve, especially through periods of transition. As a leader, I have found my own role changing as challenges on the team change—around every four months I realize everything is fundamentally different, and the way I need to spend my time changes, too.

    Recently the number of my direct reports more than doubled, and I added two different roles reporting to me. This was a very obvious instance of change, and I opened up a discussion on our team blog about what that meant. I confessed to certain things I had noticed about myself when I felt overwhelmed, and asked them four questions:

    – What do you see as the most important thing(s) I do (generally)?
    – What are the most impactful things I do for you specifically?
    – What is one thing you think I should stop doing?
    – What is the biggest area of your work where you want/need me to support you?

    But even when it’s not as obvious, your job as a manager can still evolve. Maybe you used to have mostly new managers reporting to you, and now they’ve found their feet, meaning you can be less involved and spend your time on something else instead. Maybe your team had some kind of pressing problem—a big project with a looming deadline or bad releases that needed to be fixed—but now it’s on track, so what do you focus on next?

    Continue reading…

  • Answer these 10 questions to understand if you’re a good manager

    My latest in Quartz…

    Something I struggled with as a new manager was finding a sense of accomplishment, and as I’ve moved on to manage managers, I’ve seen this become a challenge for them, too. It’s hard to find the right success metrics upon which to judge our work because our output is to make the team better, and so hopefully we give credit generously to them.

    Without success metrics beyond the team’s improvement, though, it can be be easy to feel like you’re just riding a wave of good people doing good work without contributing anything yourself.

    Some managers deal with this feeling by seeing their success metric as being available to their teams 24/7 (unsustainable), or by counting lines of code (which would be like editors focusing on the number of words they wrote themselves—absurd). Some embrace the performance of management without understanding the underlying motivations. They “perform good manager” in one-on-one meetings, team stand-up meetings, and feedback cycles, but it doesn’t really make them feel accomplished, and it’s hard to put a finger on why.

    To that end, I’ve compiled a list of signs that I look for in managers on my teams that suggest they’re doing a good job.

    Continue reading…

  • The first two questions to ask when your team is struggling

    Screen Shot 2018-10-02 at 07.50.36.png

    My second article in Quartz…

    I’ve never stepped into a leadership role without it quickly becoming clear why a new leader was needed. I think it’s normal for companies to hire new leaders when there are problems that need to be addressed. So I suspect that as the congratulations die down, it’s also normal to look at the set of problems that surround you and ask, “Where do I begin?” (also normal: “What have I done?!”). I suggest instead starting with these two questions:

    • How do I create clarity?
    • How do I create capacity?

    Continue reading…

    Thanks to @beaulebens whose questions and observation inspired this thinking and to @folletto for the helpful structural feedback.

  • Understanding how process impacts outcome can help avoid useless meetings

    Capture d’écran 2018-09-23 à 19.38.38.png

    My first article in Quartz!

    Earlier this year, when I was learning how to facilitate a specific type of workshop, a colleague revealed the secret to making it great: understanding the outcome and keeping it in mind throughout the entire process.

    If the team isn’t focused on the outcome, than they’re just performing a process.

    Now, I see this phenomenon not just in workshops that I attend or facilitate, but everywhere.

    Management is full of mechanics that could easily become process performances. One-on-one meetings. Feedback cycles. Team meetings. Retrospectives. These are not inherently useful activities (and I’m sure we’ve all been in some of these that felt extremely pointless). They are useful only in service of some kind of outcome.

    The key is to consider the outcome as you design the process, and to pay close attention to the behaviors that emerge as you introduce the process. Behaviors are the link between processes and outcomes—processes encourage behaviors that create outcomes.

    Continue reading…

    Thanks to Belinda, @folletto, and @mnowster who helped clarify my thinking.

  • On Boiling Frogs and Drowning Rats

    232636845_5ca3c4fe51_o.jpg
    Credit: Flickr / Mad Visions

    Beau recently tweeted an observation I made to him, which people reacted to… Something to do with “plague animals” all “ending up dead”. And well… maybe it isn’t my best management metaphor.

    It’s a metaphor for how we expand people’s comfort zones – the way we want to give people more responsibility gradually, as it feels possible.

    I suspect most high achievers have a point where we go from energised to so overwhelmed by everything we grind to a halt. Keeping people (especially new managers) in the space where they are energised, and catching as they head towards overwhelm is part of the job. It’s great if people will realise it themselves and surface it, but if we haven’t built a relationship such that they feel they can bring it to us… what are they going to do?

    This is the failure mode – people drown in the sea of things they have to do, with nowhere to turn.

    Some people like to be thrown in the deep end to figure it out, but thinking about this metaphor I realise that people who thrive when thrown in like rats are people who have built up their own resiliency and support. They’re not really being thrown in, because they have a parachute to deploy and a support team on standby, ready to help.

    Which also clarifies that part of the frog boiling is to help people develop resilience – and a support network. I tell everyone around me that when their job gets harder, they should make a friend. Coaching is also amazing for helping develop resilience (and self awareness) and I encourage everyone to take advantage of it (if they can). But as a manager, how you react to the inevitable failures of people on your team – do you react with kindness, understanding, and coaching?

    Or do you do you take your broken trust out on the person, destroying the relationship between you in the process?

    How do you react to your own failures? Do you display the same accountability and commitment to learn that you ask of them? Or do you embrace a double standard?

    As I think more about this metaphor, I see that the art of change management is the art of frog boiling. As much as we might be tempted to throw grenades in there “for speed”, consistent temperature and stirring will yield the highest number of live, temperature resilient frogs.

  • Towards Productive Technical Discussions

    Note: I wrote this post for an internal team blog, but thought it was worth sharing more widely.

    wool-2197757_1920.jpg
    Credit: Pixabay / congerdesign

    Part of getting to good code reviews is some up front discussion about trade-offs and implications for bigger architectural changes. I think of code review as when “my” code becomes “our” code – for architecture, those conversations need to start earlier. We all live with it, decisions have consequences beyond the project we are currently working on, and it has a huge impact on our ability to execute over time.

    Some things to think about when giving feedback:

    Ask questions. If it’s not clear to you 1) it’s probably not just you 2) it’s still worth clarifying.

    Think further out. How does the proposal affect things in 6 months? 12? We might choose a shorter term option, but we should make a mindful choice.

    Consider the effort vs the impact. I think this is a really important skill as an engineer or designer that I expect everyone on the team to have some sense of. We hire experienced people who we can trust to be autonomous, and I think this skill is pretty critical to that level of trust and autonomy.

    Don’t nitpick. Small details are distracting. Big picture feedback is more important. If something is a nitpick, clearly mark it as such – and then consider whether it’s worth nitpicking at all. When that nitpicking can be automated, let’s do that. It’s fine to be reminded by a script. It’s not a good use of anyone’s time to be reminded by another human.

    Style guides. It’s easy to have opinion on style, but consistency is more impactful than the details of it. The purpose of a style guide is to never discuss it again. Every other discussion should focus on the substance of what is being proposed, not style.

    We need to be less afraid to give people feedback in general. Technical feedback is a great place to start since 1) that is our focus 2) it is not personal. You can question and critique someone’s idea or proposal without attacking them as a person, and being able to have our ideas and proposals critiqued without taking it personally is important for any professional. We don’t have to agree with each other on everything in order to treat each other with consideration and respect.

     

    Some things to think about when asking for feedback:

    Put it in the right place. Small changes are best discussed in PRs. Bigger changes are for the internal blog (but as an OSS project should be in the README architecture document once decided).

    Be clear about the problem you’re addressing. This is really helpful context for people to understand where you’re coming from.

    Explain why it’s important. Make a case for the impact, and why now.

    Talk about what you’ve considered. What are the alternatives and their tradeoffs? Why do you think this is the best option?

    Think about the kind of feedback you want. What would be most helpful? What might other people have more knowledge of?

    Be clear on next steps. When do you need to make a decision? What do you expect to happen next? Who do you need to agree / help?

    Making Decisions

    The goal of these discussions is to define a path forward, and they should end with a specific decision which we then act on. Non-decision decisions* are a common dysfunction that I strongly prefer we avoid. Have some back and forth, switch to a call if necessary, but at the end of the thread there should be a decision and some next actions. Review the feedback, answer the questions, and then based on that, circle back, summarize, and state the decision.

    If the thread has been productive, and people feel heard, this might still feel scary but at this point we have all explained our point of view, and should be willing to accept the outcome.

    * Non-decision decisions: where a decision is made by not making a decision.