Header Image

Great Leaders Ask Great Questions

May 20, 2016 by lsmit@wemanity.com in  Blog

For the last few years, I’ve been working with and studying some of the best teams in the world; Red Arrows teams, SAS and US Navy SEAL units, Racing yacht crews, a Formula One pit crew, etc. I set out to study teamwork. In particular, I wanted to know how these teams have become world class. In the course of my studies, I identified six common characteristics, which differentiated these incredible teams.

Interestingly, I didn’t set out to study world class leadership. However, when I found world class teams, I also found world class leadership (I know, I probably should have expected that!). So, as well as studying teamwork, I also began to look at the characteristics that differentiated world class leadership. One of the most powerful insights that I discovered is this…

Great Leaders Ask Great Questions.

In fact, the great leaders that I encountered often didn’t provide any answers! Instead, they realise that the group has the potential to generate a better answer than they could on their own. It’s a principle that James Surowiecki outlines in his book, Wisdom of Crowds. When I shared this idea at an educational conference last year, a Head Teacher responded by saying, “That’s rubbish. Are your trying to tell me that Einstein should ask his class for the answer, and that the class will have a better answer than Einstein?”. “No”, I said, “Einstein is part of the class. So by engaging the class you get Einstein plus the class, not instead”.

Knowing that great leaders ask questions is one thing. Knowing what constitutes a ‘Great Question’, is another. So, what makes a question ‘Great’?

Here are some of my thoughts and reflections…

To me, ‘Great Questions’ are simply the right question, asked at the right time. To ask great questions, we need to understand the problem we’re trying to solve and where we are in the process. Do we need to ask a strategic question, or a tactical question, or one that’s related to implementing and executing a plan?

Strategic Question – Why?

Tactical Questions – What? …. How?

Action & Implementation Questions – Where? …. Who? …. When?

Very simply, it makes sense to understand why we are doing something (and whether we should be doing it), before deciding what we’re doing or how we will do it? Equally, it makes sense to know what we’re going to do, before deciding who will do it, when and where.

To me, ‘Great Questions’ are also well defined and simple. Sometimes it takes time and thought to frame a question well. The world class leaders that I saw at work often ask simple questions, which engage their team to collectively solve a problem. Some of the most powerful questions I’ve heard simply begin with the words, “How could we…?”.

To find out more, read Stronger Together; How Great Teams Work and hear from world class leaders sharing their wisdom on Be World Class TV.

By: Simon Hartley, Founder of Be World Class.

http://www.be-world-class.com/node/251

Company culture: an open and shut model

May 20, 2016

There are nine and sixty ways of constructing tribal lays,
And every single one of them is right!

Rudyard Kipling, In the Neolithic Age

How many ways can you categorise the ways that different startups organise themselves, the different flavours and colours of organisational culture adopted by companies through their life (and death). Far more than nine and sixty, I assure you. And, yes, each of them is right. Models of the world are usually helpful in making sense of the continuous chaos of reality.

I’d like to propose a very simple and useful model for startup (and, more widely, company) cultures, that I feel is relevant at this point in history: open and closed.

hierarchical-pyramid

Closed cultures

There are a number of ways to run a closed culture, but the presence of any of the following features is usually a clear sign of an at least partially closed culture:

– Secrecy by default: Business information is closed by default, on a need-to-know basis. Typically, only the senior management team has access to all the information (e.g. salaries and bonuses, detailed financials of the organisation, etc). These multi-layered secrets often form part and parcel of the power structure: the higher you are, the more information you have access to.

– Top-down, hierarchical management: This can be implemented with varying degrees of flexibility, but the common element is the idea that you have a boss and you should do what they tell you. All closed cultures enable some elements of push-back from those savvy enough to know how to make their points from below, but the general mode of functioning is from the top to the bottom.

– The Pyramid/Career Ladder: Closed organisations are without fail mapped out as pyramid-shaped: there is one CEO at the top, with a senior executive team below, and progressively wider layers as you go down. This Pyramid also provides the Career Ladder – the ever-receding MacGuffin that motivates people to work hard so they can one day get on top of the Pyramid and finally achieve true Success.

– Focus on profit: The more advanced closed organisations tend to focus on profit above all. This is measured as a number and is the primary driver of decision-making. If an action results in more profit, it’s worth doing. If the company makes more profit, it is more successful. Profit is the essential driver of all decisions. “How will it affect the bottom line?” is the main (or perhaps even only) question being asked.

– Motivational measurements and individual incentives: Closed organisations, as they mature, learn to apply measurements as a method of ensuring performance. They will measure everything that can be measure and make up targets and projections (with varying degrees of involvement from those being measured), then hold people accountable to those estimates. Those who meet their targets are rewarded, and those who fail are punished.

– Fixed roles and masks: In closed cultures, you are hired for a specific role. You can progress towards more managerial responsibilities through promotion, but typically, doing things outside of your role is discouraged (if only because it will step on the toes of the person who currently owns that role). In closed organisations you are your role. It’s no surprise, then, that most people put on a mask to go to work: while they are at the office, they are no longer a full person with a variety of wants and activities and aspirations, but a “Web Developer” or a “Marketing Manager”. Professional behaviour is all that’s accepted, and it’s all that’s given.

– Distrust and control: A fundamental assumption of closed cultures is that people are lazy and cannot be trusted, so they need to be controlled, otherwise they will not do any work. This gives even more justification to adding more measurements and narrowly defining roles and performance criteria. When they don’t treat them like mindless cogs in a machine, closed cultures tend to treat employees like irresponsible children.

There are countless examples of closed cultures: most of the companies and organisations in the world are run on the closed model. In fact, in many countries it is illegal to run a public company in an open way .  You’ve most likely worked for a closed company at some point in your life. In fact, chances are you’re working in one right now.

Whilst closed cultures (which form the majority of business cultures today) are clearly capable of delivering great results, they have a number of deadly flaws, which I’ll cover in more detail in a later article. For now, let’s look at open cultures.

Open cultures

If there are many ways to run a closed culture, there are even more ways to run an open one. Each open company tends to have its own way of expressing its culture. However, these are some typical commonalities by which to recognise an open culture:

– Transparency by default: In open cultures, business information is publicly available to all employees. This includes salaries, but also bad news, strategic plans, problems, decisions, ideas, etc. People are trusted to be able to handle that information.

– Flat hierarchy and/or self-management: If everyone knows everything and you’ve hired smart people in the right kinds of jobs, it is very difficult to maintain an arbitrary hierarchy, since everyone can contribute to any decision. When you trust people, it is also unnecessary to set up managers whose job it is to check after them.

– Personal development through work: When there is no career ladder, how do people achieve career progression? The obvious solution is that they take on more responsibilities without having to go “up” an arbitrary ladder. As a natural consequence of that, it is possible for people to fully express themselves in their work, by getting involved in their full range of interests, so they can achieve more personal development than they would in a narrow role with a career ladder.

– Multiple stakeholders, values, and purpose: In open organisations, the idea of valuing profit above all others becomes obviously absurd. It’s not only shareholders, but also employees, suppliers, customers, society, and the environment, which matter. The company does not exist in a vacuum. Values become a way to express what the company cares about, rather just a motivational slogan. Along with the higher purpose of the company, they become the way that decisions get made in open cultures.

– Team or company incentives: There is a progression from the closed culture approach of individual incentives, via team incentives, towards the eventual ideal, which is a system where base pay is determined by a combination of what the person is contributing, what the person needs, and what the company can afford, along with company-wide bonuses. Individual incentives are shunned.

– Self-determined pay: One of the surefire signs of an open culture is when people determine their own pay. In most companies, this is unthinkable. In open cultures, it becomes a natural consequence of all the other stuff. After all, if you trust people to make all sorts of important decisions about the company, why not trust them to make this decision too?

– Separation of role and person: The idea that a person and their role are intrinsically bound becomes visibly stupid as the culture opens up. Eventually, it is clear that people are not their roles, but are capable of engaging in several roles simultaneously, contributing more fully to the organisation’s needs. This further enables people to accomplish themselves and to be fully themselves at work instead of wearing masks. One of the ways this is accomplished is through Open Allocation.

– Trust: Perhaps most important is the fact that open cultures treat employees like adults, trusting them to do the right thing even in complex or ambiguous situations. There are of course processes to help people make better decisions, but the key point is that all these processes start from a perspective of trust and responsibility.

The benefits of running companies this way ought to be obvious, but in case they need to be spelled out:

– People in open cultures are more engaged, happier, more creative, they contribute more, etc. This makes them much more fun to work in, both as a founder and as an employee, but also much more productive – people work much more effectively when they care.

– Having a better environment makes it easier to hire great people.

– Open cultures are way more adaptable to change. Change management is an oxymoron in an open culture: change happens constantly and continually, not through expensive, long-winded, and often failure-prone change processes.

– Because they motivate people so much better, open cultures are, ironically, also better at achieving sustainable, long-term financial results.

There are some examples of open cultures out there, too, to varying degrees.GrantTreeBuffer, Valve and Github, in the startup space, are known examples of open cultures. Others include Semco, Burtzorg, Happy Startup, MorningStar, and many others in all sorts of different contexts and sizes. All companies could adopt an open culture, but most don’t. Why is that?

Reinventing Organisations, by Frederic Laloux, studies a dozen or so open cultures and comes to the conclusion that two things are absolutely prerequisite for an open culture to exist for any length of time: both the CEO/Leader and the owners must be fully supportive of this (currently) unconventional way of operating. Otherwise, eventually the company hits a hard time, and either the CEO or the owners pressure it into returning to a more traditional (i.e. closed) mode of functioning. So the obvious reason why more companies are not currently open is because most CEOs are not prepared to let go of their control mindset, and when they are, the owners (whether private owners or VCs with board seats and a traditional, closed mindset, or simply public markets) frequently won’t let them.

If you’re a founder of a startup, this poses an interesting challenge: are you up to the challenge of creating an open culture in your business? Even when that involves giving up the trappings of power? Even when that involves passing on an investment round from an investor whom you know will force the company to change its ways when it hits a rough patch?

If so, welcome to the club. Follow this blog, and I’ll do my best to share what I’ve learned in transforming GrantTree to be an open company. This is still a new field so we can all learn from each other.

By: Daniel Tenner from GrantTree

Company culture: an open and shut model

Your Engineering Team Is Not an Island: Success Demands a Holistic View of the Business

May 23, 2016

I just re-read the awesome post from my friends David Loftesness and Raffi Krikorian, What Does A VP of Engineering Do Again? And while I agree with everything that they say, I think there is one crucial item missing, which has been present in every job I’ve had because all of them were user-facing internet services and a majority of my job has been working with product teams. Collaboration with stakeholders (especially with product) is key, but if you take it one step further, a VP of Engineering is actually measured by execution in a wider context across many teams or departments. You cannot look at engineering in isolation for your successes or failures.

But first a short story about my first months at SoundCloud. The CTO wanted more front-end work done because an important release was nearing. He asked me to hire more engineers to accomplish that goal. I started recruiting, but then I looked at why the velocity of the existing team was not meeting expectations. So, I went to all of the front-end teams (at that time it was Web, iPhone, and Android) and asked a very simple question “What slows you down the most in your day-to-day work?” To my surprise, everyone gave the same answer “We only have one designer.” They went on to say that although the designer was very good, she was completely overloaded so designs, changes, and simple clarifications took forever to get done.

Now that I knew design was actually the cause for delays, the solution to my problem was not to hire more engineers (which might have even made the problem worse with more work for the designer), but to start building a design team.

Engineering leads need to look at the whole product process (together with the responsible stakeholders) and not just at engineering in isolation. What I did was a very simple (but, in this case, effective) form of value stream mapping. Our self-improvement at SoundCloud continued. You can read Phil Calcado’s excellent post about the organizational aspects of microservices at SoundCloud.

The Best Engineering Leads Will Stop and Assess the Situation

Continually assessing situations in a holistic way isn’t just the job of an engineering lead — everybody involved should take responsibility. But, in my experience, the problem usually surfaces in engineering because when things are not moving fast enough (and when do they ever?) management’s first reaction can be to throw more engineers at the problem so more work will get done, but also (and this is the not so nice scenario), management thinks the engineers are not working hard enough. Other common responses from management include reorganizing the teams or adopting new methodologies. However, as an engineering leader, you are a lot like a doctor: you need to diagnose the illness before treating the symptoms.

Engineering leaders need to look at the whole value chain and to sit with the leaders from affected departments to review at the problem. The solution to a problem might not be to hire more people (which a lot of startups do), but to organize product development in a better way. And if you have to hire, it might mean that you have to move headcount around. When everyone has the same goal goal — delivering more business value — shifting headcount from engineering to design or to recruiting shouldn’t be an issue. Afterall, the goal is more business value, not having the biggest department. So, when I realized our problem at SoundCloud wasn’t going to be fixed by adding more engineers, we created a design team. But this was just the first step towards a better setup.

Even after creating a larger design team, it remained isolated from other departments and was not fully integrated with our workflows. The problems of turnaround and wasted resources were exacerbated by the increasing risk of misalignment between product, design, and engineering. Therefore, the next logical step was to improve the organization by creating a delivery team per product.

Shifting Organizational Structures to Deliver Business Value

A delivery team is a team that can deliver the vast majority (95%) of its backlog items to production without dependencies on other teams. Unlike more horizontally-oriented teams (for example, a front-end engineering team that relies on the back-end engineering team for any back-end changes), a delivery team has all the necessary skills inside their team. So, depending on your company and your product, these teams can look very different. In engineering teams that are infrastructure focused, these teams can consist of only engineers; but if you look at a team that delivers a consumer-facing web app, then the team looks more like this:

Traditional and Delivery Team Structure

Creating these delivery teams and then making sure you have the right staffing for them should eliminate a staffing mismatch between the affected departments. Some team members (like support) might just be a pointperson for the team, e.g., the support person only attends the daily standup and reports what is going on.

So, don’t look at engineering in isolation when trying to solve delivery problems. It is critical that each engineering leader (and especially the VP of Engineering, who can really influence the organizational setup) ensures that the overall product development process is set up in a way that reduces waste and delivers value to the customer which is the whole point of product development in the first place!

This post includes material from the upcoming book “Scaling Teams” by myself and David Loftesness, which will be published by O’Reilly in 2016. In this book, we will explain in detail the various scaling challenges of software startups.

Thanks to Laurel Ruma and David Loftessness

By: Alexander Grosse from issuu

https://medium.com/scaling-teams/your-engineering-team-is-not-an-island-success-demands-a-holistic-view-of-the-business-bccd6116094b#.9tbmcbfnw

 

 

Brace yourself Spark the change is coming..To France!

Nov 22, 2017

 

 


Also published on Medium.