Quality is primarily viewed in terms of corporate culture, multi-departmental ad-hoc task forces and the salvation of entire companies. This article, instead, will view these ideas as they might be applied by a Team Leader with a small permanent staff.
Quality has become the philosophers' stone of management practice with consultants and gurus vying to charm lead-laden corporations into gold-winning champions. Stories abound of base companies with morose workers and mounting debts being transformed into happy teams and healthy profits; never a day goes by without a significant improvement, a pounds-saving suggestion or a quantum leap in efficiency. With this professed success of 'Quality' programmes, there has evolved a proscriptive mythology of correct practise which has several draw backs:
the edicts call for nothing less than a company wide, senior-management led programme
the adherence to a single formula has a limited effect, precludes innovation outside these boundaries, and reduces the differentiation which such programmes profess to engender
the emphasis on single-task, specially formed groups shifts the focus away from the ordinary, daily bread-and-butter
Of course, these criticisms do not invalidate the ideas of Quality but are simply to suggest that the principles might well be viewed from a new angle - and applied at a different level. This article attempts to provide a new perspective by re-examining some of the tenets of Quality in the context of a small, established team: simply, what could a Team Leader do with his/her staff.
What is 'Quality'?
In current management writings 'Quality' has come to refer to a whole gambit of practices which themselves have resulted in beneficial side-effects; as a Team Leader, you will want to take advantage of these benefits also.
The Customer
In simple terms, attaining Quality has something to do with satisfying the expectations of the customer. Concern for the wishes and needs of customers becomes the focus for every decision. What the customer wants, the company provides. This is not philanthropy, this is basic survival. Through careful education by competitors, the customer has begun to exercise spending power in favour of quality goods and services; and while quality is not the sole criterion in selecting a particular supplier, it has become an important differentiator.
If one ten-pence ball-point runs dry in one month and another ten-pence ball-point lasts for three then the second ball-point is the make which the customer will buy again and which he/she recommends to others - even if it costs a little more. The makers of the first ball-point may have higher profit margins, but eventually no sales; without quality in the product, a company sacrifices customers, revenue and ultimately its own existence. In practical terms, Quality is that something extra which will be perceived by the customer as a valid reason for either paying more or for buying again.
In the case where the product is a service, Quality is equated with how well the job is done and especially with whether the customer is made to feel good about the whole operation. In this respect Quality often does cost more, but the loss is recouped in the price customers are prepared to pay and in the increase of business.
Reliability
The clearest manifestation of Quality is in a product's reliability: that the product simply works. To prevent problems from arising after the product is shipped, the quality must be checked before-hand - and the best time to check quality is throughout the whole design and manufacturing cycle. The old method of quality control was to test the completed product and then to rework to remove the problems. Thus while the original production time was short, the rework time was long. The new approach to quality simply asserts that if testing becomes an integral part of each stage of production, the production time may increase but the rework time will disappear. Further, you will catch and solve many problems which the final 'big-bang' quality-check would miss but which the customer will find on the first day.
To achieve this requires an environment where the identification of errors is considered to be 'a good thing', where the only bad bugs are the ones which got away. One of the most hallowed doctrines of Quality is that of zero defects. 'Zero defects' is a focus, it a glorious objective, it is the assertion that nothing less will suffice and that no matter how high the quality of a product, it can still be improved. It is a paradox in that it is an aim which is contrary to reason, and like the paradoxes of many other religions it holds an inner truth. This is why the advocates of Quality often seem a little crazy: they are zealots.
People as Resource
While Quality has its own reward in terms of increased long-term sales, the methods used to achieve this Quality also have other benefits. In seeking to improve the quality of the product, manufacturers have found that the people best placed to make substantial contributions are the workforce: people are the most valuable resource. It is this shift in perspective from the management to the workforce which is the most significant consequence of the search for quality. From it has arisen a new managerial philosophy aimed at the empowerment of the workforce, decision-making by the front line, active worker involvement in the company's advancement; and from this new perspective, new organizational structures have evolved, exemplified in 'Quality Circles'.
Without digressing too much, it is important to examine the benefits of this approach. For such delegation to be safely and effectively undertaken, the management has to train the workforce; not necessarily directly, and not all at once, but often within the Quality Circles themselves using a single 'facilitator' or simply peer-coaching. The workforce had to learn how to hold meetings, how to analyse problems, how to take decisions, how to present solutions, how to implement and evaluate change. These traditionally high-level managerial prerogatives are devolved to the whole staff. Not only does this develop talent, it also stimulates interest. Staff begin to look not only for problems but also for solutions. Simple ideas become simply implemented: the secretary finally gets the filing cabinet moved closer to the desk, the sales meetings follow an agenda, the software division creates a new bulletin board for the sports club. The environment is created where people see problems and fix 'em.
Larger problems have more complex solutions. One outcome of the search for Quality in Japan is the system of Just-In-Time flow control. In this system, goods arrive at each stage of the manufacturing process just before they are needed and are not made until they are needed by the next stage. This reduces storage requirements and inventory costs of surplus stock. Another outcome has been the increased flexibility of the production line. Time to change from one product run to the next was identified as a major obstacle in providing the customer with the desired range of products and quantities, and so the whole workforce became engaged in changing existant practices and even in redesigning the machinery.
The Long Term
However, I believe that the most significant shift in perspective which accompanies the introduction of Quality is that long term success is given precedence over short term gains. The repeat-sale and recommendation are more important than this month's sales figures; staff training and development remain in place despite immediate schedule problems; the product's reliability is paramount even over time-to-market. Time is devoted today to saving time in the future and in making products which work first and every time.
Team Quality
While the salvation of an entire corporation may rest primarily with Senior Management, the fate of a team rests with the Team Leader. The Team Leader has the authority, the power to define the micro-culture of the work team. It is by the deliberate application of the principles of Quality that the Team Leader can gain for the team the same benefits which Quality can provide for a corporation.
The best ideas for any particular team are likely to come from them - the aim of the Team Leader must be to act as a catalyst through prompts and by example; the following are possible suggestions.
Getting Started
There will be no overnight success. To be lasting, Quality must become a habit and a habit is accustomed practise. This takes time and training - although not necessarily formal training but possibly the sort of reinforcement you might give to any aspect of good practise. To habituate your staff to Quality, you must first make it an issue. Here are two suggestions.
The first idea is to become enthusiastic about one aspect at a time, and initially look for a quick kill. Find a problem and start to talk about it with the whole team; do not delegate it to an individual but make it an issue for everybody. Choose some work-related problem like 'how to get the right information in time' and solicit everybody's views and suggestions - and get the problem solved. Demand urgency against a clear target. There is no need to allocate large amounts of resource or time to this, simply raise the problem and make a fuss. When a solution comes, praise it by rewarding the whole team, and ensure that the aspects of increased efficiency/productivity/calm are highlighted since this will establish the criteria for 'success'. Next, find another problem and repeat.
The second idea is the regular weekly meeting to discuss Quality. Of course meetings can be complete time wasters, so this strategy requires care. The benefits are that regularity will lead to habit, the formality will provide a simple opportunity for the expression of ideas, and the inclusion of the whole group at the meeting will emphasize the collective responsibility. By using the regular meeting, you can establish the 'ground rules' of accepted behaviour and at the same time train the team in effective techniques.
One problem is that the focus on any one particular issue may quickly loose its efficacy. A solution is to have frequent shifts in focus so that you maintain the freshness and enthusiasm (and the scope for innovative solutions). Further benefits are that continual shifts in emphasis will train your team to be flexible, and provide the opportunity for them to raise new issues. The sooner the team takes over the definition of the 'next problem', the better.
Initial Phases
The initial phases are delicate. The team will be feeling greater responsibility without extra confidence. Thus you must concentrate on supporting their development. Essentially you will be their trainer in management skills. You could get outside help with this but by undertaking the job yourself, you retain control: you mould the team so that they will reflect your own approach and use your own criteria. Later they will develop themselves, but even then they will understand your thinking and so your decisions.
One trap to avoid is that the team may focus upon the wrong type of problem. You must make it clear any problem which they tackle should be:
related to their own work or environment
something which they can change
This precludes gripe sessions about wages and holidays.
As with all group work, the main problem is clarity. You should provide the team with a notice board and flip-charts specifically for Quality problems. These can then be left on display as a permanent record of what was agreed.
If you can, steer the group first to some problem which has a simple solution and with obvious (measurable) benefits. A quick, sharp success will motivate.
Team Building
To succeed, a Quality push must engage the enthusiasm of the entire team; as Team Leader, you must create the right atmosphere for this to happen. Many aspects of team building can be addressed while Quality remains the focus.
You must create the environment where each team member feels totally free to express an idea or concern and this can only be done if there is no stigma attached to being incorrect. No idea is wrong - merely non-optimal. In each suggestion there is at least a thread of gold and someone should point it out and, if possible, build upon it. Any behaviour which seeks laughter at the expense of others must be swiftly reprimanded.
One crude but effective method is to write down agreed ground rules and to display them as a constant reminder for everyone, something like:
all criticism must be kind and constructive
all our-problems are all-our problems
BUGS WANTED: DEAD OR ALIVE (but not for long)
if it saves time later, do it now
Another method is to constantly talk about the group as the plural pronoun: 'we decided', 'we can do this', 'we'll get back to you'. This is especially effective if it is used in conversation with outsiders (especially management) within ear-shot of the team. Praise and reward the whole team; get the team wider fame by a success story in an internal newspaper.
Most importantly, you must enable failure. If the team is unable to try out ideas without rebuke for errors, then the scope of their solutions will be severely limited. Instead, a failure should be an opportunity to gain knowledge and to praise any safe-guards which were included in the plan.
Mutual Coaching
An important aspect of team interaction is the idea of mutual support. If you can instill the idea that all problems are owned by the entire team then each member will be able to seek help and advice when needed from every other team member. One promoter of this is to encourage mutual coaching. If one team member knows techniques or information which would be useful to the rest, then encourage him/her to share it. Specifically this will raise the profile, confidence and self-esteem of the instructor at the same time as benefiting the entire group. And if there is one member who might never have anything useful to impart - send him/her to a conference or training session to find something.
Statistics
One of the central tenets of Quality programmes is the idea of monitoring the problem being addressed: Statistical Quality Control. Quite simply, if you can't measure an improvement, it probably isn't there. Gathering statistics has several benefits in applying Quality:
it identifies (the extent of) the problem
it allows progress to be monitored
it provides an objective criterion for the abandonment of an idea
it can justify perceived expense in terms of observed savings/improvements
it motivates staff by providing a display of achievement
and, of course, some problems simply disappear when you try to watch them.
The statistics must be gathered in an objective and empirical manner, the outcome should be a simple table or graph regularly updated to indicate progress, and these results must be displayed where all the team can watch. For example, if your team provides product support, then you might monitor and graph the number of repeat enquiries or the average response time. Or if you are in product development, you might want to monitor the number of bugs discovered (i.e. improvement opportunities).
In the long term, it may be suitable to implement the automatic gathering of statistics on a wide range of issues such as complaints, bug reports, machine down-time, etc. Eventually these may either provide early warning of unexpected problems, or comparative data for new quality improvement projects. It is vital, however, that they focus upon an agreed problem and not upon an individual's performance or else all the positive motivation of staff involvement will be lost.
Projects
Clarity of purpose - this is the key to success. You need a simple, stated objective which everybody understands and which everybody can see achieved.
Any plan to improve the quality or effectiveness of the group must contain:
the objective
the method
the statistical display for monitoring the outcome
the agreed criteria for completion or curtailment
By insisting on this format, you provide the plan-owners with a simple mechanism for peer recognition (through the displayed notice board) and yet enable them to manage their own failure with grace.
For a small established team, the 'customer' includes any other part of the company with which the team interacts. Thus any themes regarding customer satisfaction can be developed with respect to these so called internal customers. In the end, the effectiveness of your team will be judged by the reports of how well they provide products for others.
A simple innovation might be for a member of your team to actually talk to someone from each of these internal customer groups and to ask about problems. The interfaces are usually the best place to look for simply solved problems. The immediate benefit may be to the customer, but in the long run better communications will lead to fewer misunderstandings and so less rework.
Building Quality
Quality costs less than its lack; look after the pennies and the profits will take care of themselves. To build a quality product, you must do two things:
worry the design and the procedures
include features to aid quality checking
It is a question of attitude. If one of the team spots a modification in the design or the procedures which will have a long term benefit, then that must be given priority over the immediate schedule. The design is never quite right; you should allocate time specifically to discussing improvement. In this you should not aim at actual enhancements in the sense of added features or faster performance, but towards simplicity or predicting problem areas. This is an adjunct to the normal design or production operations - the extra mile which lesser teams would not go.
Many products and services do not lend themselves to quality monitoring. These should be enhanced so that the quality becomes easily tracked. This may be a simple invitation for the 'customer' to comment, or it could be a full design modification to provide self-checking or an easy testing routine. Any product whose quality can not be tracked should naturally become a source of deep anxiety to the whole team - until a mechanism is devised.
One of the least-used sources of quality in design and production in the engineering world is documentation. This is frequently seen as the final inconvenience at product release, sometimes even delegated to another (non-technical) group - yet the writing of such documentation can be used as an important vehicle for the clarification of ideas. It also protects the group from the loss of any single individual; the No.7 bus, or the head-hunter, could strike at any time.
In devising a mechanism for monitoring quality, many teams will produce a set of test procedures. As bugs emerge, new procedures should be added which specifically identify this problem and so check the solution. Even when the problem is solved the new procedures should remain in the test set; the problem may return (perhaps as a side effect of a subsequent modification) or the procedure may catch another. Essentially the test set should grow to cover all known possibilities of error and its application should, where possible, be automated.
Role Change
As your team develops, your role as leader changes subtly. You become a cross between a priest and a rugby captain, providing the vision and the values while shouting like crazy from the centre of the field. Although you retain the final say (that is your responsibility), the team begins to make decisions. The hardest part, as with all delegation, is in accepting the group decision even though you disagree. You must never countermand a marginal decision. If you have to over-rule the team, it is imperative that you explain your reasons very clearly so that they understand the criteria; this will both justify your intervention and couch the team in (hopefully) good decision-making practices.
Another role which you assume is that of both buffer and interface between the team and the rest of the company: a buffer in that you protect the team from the vagaries of less enlightened managers; an interface in that you keep the team informed about factors relevant to their decisions. Ultimately, the team will be delegating to you (!) tasks which only you, acting as manager, can perform on its behalf.
Quality for Profit
By applying the principles of Quality to an established team, the Team Leader can enjoy the benefits so actively sought by large corporations. The key is the attitude - and the insistence on the primacy of Quality. As a Team Leader, you have the power to define the ethos of your staff; by using Quality as the focus, you also can accrue its riches.
Gerard M Blair is a Senior Lecturer in VLSI Design at the Department of Electrical Engineering, The University of Edinburgh. His book Starting to Manage: the essential skills is published by Chartwell-Bratt (UK) and the Institute of Electrical and Electronics Engineers (USA).

The first steps to becoming a really great manager are simply common sense; but common sense is not very common. This article suggests some common-sense ideas on the subject of great management.
The major problem when you start to manage is that you do not actually think about management issues because you do not recognize them. Put simply, things normally go wrong not because you are stupid but only because you have never thought about it. Management is about pausing to ask yourself the right questions so that your common sense can provide the answers.
When you gain managerial responsibility, your first option is the easy option: do what is expected of you. You are new at the job, so people will understand. You can learn (slowly) by your mistakes and probably you will try to devote as much time as possible to the rest of your work (which is what your were good at anyway). Those extra little 'management' problems are just common sense, so try to deal with them when they come up.
Your second option is far more exciting: find an empty telephone box, put on a cape and bright-red underpants, and become a SuperManager.
When you become a manager, you gain control over your own work; not all of it, but some of it. You can change things. You can do things differently. You actually have the authority to make a huge impact upon the way in which your staff work. You can shape your own work environment.
In a large company, your options may be limited by the existing corporate culture - and my advice to you is to act like a crab: face directly into the main thrust of corporate policy, and make changes sideways. You do not want to fight the system, but rather to work better within it. In a small company, your options are possibly much wider (since custom is often less rigid) and the impact that you and your team has upon the company's success is proportionately much greater. Thus once you start working well, this will be quickly recognized and nothing gains faster approval than success. But wherever you work, do not be put off by the surprise colleagues will show when you first get serious about managing well.
STARTING A REVOLUTION
The idea of starting alone, however, may be daunting to you; you may not see yourself as a David against the Goliath of other peoples' (low) expectations. The bad news is that you will meet resistance to change. Your salvation lies in convincing your team (who are most effected) that what you are doing can only do them good, and in convincing everyone else that it can do them no harm. The good news is that soon others might follow you.
There is precedent for this. For instance, when a British firm called Unipart wanted to introduce Japanese methods (Honda's to be precise) into their Oxford plan (The Economist - 11th April 1992 - page 89) they sent a small team to Japan to learn what exactly this meant. On their return, they were mocked by their workmates who saw them as management pawns. So instead they were formed into their own team and sent to work in a corner of the plant where they applied their new knowledge in isolation. Slowly, but surely, their example (and missionary zeal) spread through the factory and changes followed. Now Unipart have opened a new factory and the general manger of the first factory attributes the success to 'releasing talent already on the shop floor'. Of course one can always find case studies to support any management idea, but it does exemplify the potential of a small cell of dedicated zealots - led by you.
THREE FACES OF A MANAGER
The manger of a small team has three major roles to play:
Planner
A Manager has to take a long-term view; indeed, the higher you rise, the further you will have to look. While a team member will be working towards known and established goals, the manager must look further ahead so that these goals are selected wisely. By thinking about the eventual consequences of different plans, the manager selects the optimal plan for the team and implements it. By taking account of the needs not only of the next project but the project after that, the manager ensures that work is not repeated nor problems tackled too late, and that the necessary resources are allocated and arranged.
Provider
The Manager has access to information and materials which the team needs. Often he/she has the authority or influence to acquire things which no one else in the team could. This role for the manager is important simply because no one else can do the job; there is some authority which the manager holds uniquely within the team, and the manager must exercise this to help the team to work.
Protector
The team needs security from the vagaries of less enlightened managers. In any company, there are short-term excitements which can deflect the work-force from the important issues. The manager should be there to guard against these and to protect the team. If a new project emerges which is to be given to your team, you are responsible for costing it (especially in terms of time) so that your team is not given an impossible deadline. If someone in your team brings forward a good plan, you must ensure that it receives a fair hearing and that your team knows and understands the outcome. If someone is in your team has a problem at work, you have to deal with it.
Version Two
That was rather formal. If you like formal, then you are happy. If you do not like formal then here is an alternative answer, a manager should provide:
VISION - VALUES - VERVE
Vision in that the future must be seen and communicated to the team; Values in that the team needs a unifying code of practice which supports and enhances co-operation; Verve in that positive enthusiasm is the best way of making the work exciting and fun. If you do not think your work is exciting, then we have found a problem. A better word than Verve might be Chutzpah (except that it does not begin with a 'V') which means 'shameless audacity'. Is that not refreshing? Inspiring even? A manager should dare to do what he/she has decided to do and to do it with confidence and pride.
VISION
One of the most cited characteristics of successful managers is that of vision. Of all the concepts in modern management, this is the one about which the most has been written. Of course different writters use it in different ways. One usage brings it to mean clairvoyance as in: 'she had great vision in foreseeing the demise of that market'. This meaning is of no use to you since crystal balls are only validated by hindsight and this article is concerned with your future.
The meaning of vision which concerns you as a manager is: a vivid idea of what the future should be. This has nothing to do with prediction but everything to do with hope. It is a focus for the team's activity, which provides sustained long-term motivation and which unites your team. A vision has to be something sufficiently exciting to bind your team with you in common purpose. This implies two things:
you need to decide where your team is headed
you have to communicate that vision to them
Communicating a vision is not simply a case of painting it in large red letters across your office wall (although, as a stunt, this actually might be quite effective), but rather bringing the whole team to perceive your vision and to begin to share it with you. A vision, to be worthy, must become a guiding principle for the decision and actions of your group.
Now, this vision thing, it is still a rather nebulous concept, hard to pin down, hard to define usefully; a vision may even be impractical (like 'zero defects'). And so there is an extra stage which assists in its communication: once you have identified your vision, you can illustrate it with a concrete goal, a mission. Which leads to the creation of the famous 'mission statement'. Let us consider first what is a mission, and then return to a vision.
A mission has two important qualities:
it should be tough, but achievable given sufficient effort
it must be possible to tell when it has been achieved
To maintain an impetus, it might also have a time limit so that people can pace their activity rather than getting winded in the initial push. The scope of your vision depends upon how high you have risen in the management structure, and so also does the time limit on your mission statement. Heads of multinational corporations must take a longer view of the future than the project leader in divisional recruitment; the former may be looking at a strategy for the next twenty-five years, the latter may be concerned with attracting the current crop of senior school children for employment in two-three years. Thus a new manager will want a mission which can be achieved within one or two years.
If you are stuck for a mission, think about using Quality as a focus since this is something on which you can build. Similarly, any aspects of great management which are not habitual in your team at the moment could be exemplified in a mission statement. For instance, if your team is in product design, your mission might be to fully automate the test procedures by the next product release; or more generally, your team mission might be to reduce the time spent in meetings by half within six months.
Once you have established a few possible mission statements, you can try to communicate (or decide upon) your vision. This articulates your underlying philosophy in wanting the outcomes you desire. Not, please note, the ones you think you should desire but an honest statement of personal motivation; for it is only the latter which you will follow with conviction and so of which you will convince others. In general, your vision should be unfinishable, with no time limit, and inspirational; it is the driving force which continues even when the mission statement has been achieved. Even so, it can be quite simple: Walt Disney's vision was 'to make people happy'. As a manager, yours might be something a little closer to your own team: mine is 'to make working here exciting'.
There is no real call to make a public announcement of your vision or to place it on the notice board. Such affairs are quite common now, and normally attract mirth and disdain. If your vision is not communicated to your team by what you say and do, then you are not applying it yourself. It is your driving motivation - once you have identified it, act on it in every decision you make.
PRESCIENCE
Prescience is something for which you really have to work at. Prescience is having foreknowledge of the future. Particularly as a Protector, you have to know in advance the external events which impact upon your team. The key is information and there are three type:
information you hear (tit-bits about travel, meetings, etc)
information you gather (minutes of meetings, financial figure, etc)
information you infer (if this happens then my team will need ...)
Information is absolutely vital. Surveys of decision making in companies reveal that the rapid and decisive decisions normally stem not from intuitive and extraordinary leadership but rather from the existence of an established information system covering the relevant data. Managers who know the full information can quickly reach an informed decision.
The influences upon you and your team stem mostly from within the company and this is where you must establish an active interest. Let us put that another way: if you do not keep your eyes open you are failing in your role as Protector to you team. Thus if your manager comes back from an important meeting, sit down with him/her afterwards and have a chat. There is no need to employ subterfuge, merely ask questions. If there are answers, you hear them; if there are none, you know to investigate elsewhere. If you can provide your manager with suggestions/ideas then you will benefit from his/her gratitude and future confidence(s). You should also talk to people in other departments; and never forget the secretaries who are normally the first to know everything.
Now some people love this aspect of the job, it makes them feel like politicians or espionage agents; others hate it, for exactly the same reasons. The point is that it must be done or you will be unprepared; but do not let it become a obsession.
Gathering information is not enough on its own: you have to process it and be aware of implications. The trick is to try to predict the next logical step from any changes you see. This can get very complicated, so try to restrict yourself to guessing one step only. Thus if the sales figures show a tailing off for the current product (and there are mutterings about the competition) then if you are in development, you might expect to be pressured for tighter schedules; if you are in publicity, then there may soon be a request for launch material; if you are in sales, you might be asked to establish potential demand and practical pricing levels. Since you know this, you can have the information ready (or a schedule defence prepared) for when it is first requested, and you and your team will shine.
Another way of generating information is to play 'what if' games. There are dreadfully scientific ways of performing this sort of analysis, but reasonably you do not have the time. The sort of work this article is suggesting is that you, with your team or other managers (or both), play 'what if' over coffee now and then. All you have to do is to postulate a novel question and see how it runs.
A productive variation on the 'what if' game is to ask: 'what can go wrong?' By deliberately trying to identify potential problems at the onset, you will prevent many and compensate for many more. Set aside specific time to do this type of thinking. Call it contingency planning and put in in your diary as a regular appointment.
FLEXIBILITY
One of the main challenges in management is in avoiding pat answers to everyday questions. There is nothing so dull, for you and your team, as you pulling out the same answer to every situation. It is also wrong. Each situation, and each person, is unique and no text-book answer will be able to embrace that uniqueness - except one: you are the manager, you have to judge each situation with a fresh eye, and you have to create the response. Your common sense and experience are your best guide in analysing the problem and in evolving your response.
Even if the established response seems suitable, you might still try something different. This is simple Darwinism. By trying variations upon standard models, you evolve new and potentially fitter models. If they do not work, you do not repeat them (although they might be tried in other circumstances); if they work better, then you have adapted and evolved.
This deliberate flexibility is not just an academic exercise to find the best answer. The point is that the situation and the environment are continually changing; and the rate of change is generally increasing with advancing technology. If you do not continually adapt (through experimentation) to accommodate these changes, then the solution which used to work (and which you still habitually apply) will no longer be appropriate. You will become the dodo. A lack of flexibility will cause stagnation and inertia. Not only do you not adapt, but the whole excitement of your work and your team diminish as fresh ideas are lacking or lost.
Without detracting from the main work, you can stimulate your team with changes of focus. This includes drives for specific quality improvements, mission statements, team building activities, delegated authority, and so on. You have to decide how often to 'raise excitement' about new issues. On the one hand, too many focuses may distract or prevent the attainment of any one; on the other hand, changes in focus keep them fresh and maintain the excitement.
By practising this philosophy yourself, you also stimulate fresh ideas from your team because they see that it is a normal part of the team practice to adopt and experiment with innovation. Thus not only are you relieved of the task of generating the new ideas, but also your team acquire ownership in the whole creative process.
The really good news is that even a lousy choice of focus can have a beneficial effect. The most famous experiments in management studies were conducted between 1927 and 1932 by E Mayo and others at the Hawthorne works of the Western Electric Company in Chicago. The study was originally motivated by a failed experiment to determine the effect of lighting conditions on the production rates of factory workers. This experiment 'failed' because when the lighting conditions were changed for the experimental group, production also increased in the control group where no changes had been made. Essentially, Mayo took a small group of workers and varied different conditions (number and duration of breaks, shorter hours, refreshments, etc) to see how these actually affected production. The problem was not that production was uneffected but rather that whatever Mayo did, production increased; even when conditions were returned to the original ones, production increased.
After many one-to-one interviews, Mayo deduced that the principal effect of his investigations had been to establish a team spirit amongst the group of workers. The girls (sic) who had formally worked with large numbers of others were now a small team, they were consulted on the experiments, and the researchers displayed a keen interest in the way the girls were working and feeling about their work. Thus their own involvement and the interest shown in them were the reasons for the girl's increased productivity.
By providing changes of focus you build and motivate your team. For if you show in these changes that you are actively working to help them work, then they will feel that their efforts are recognized. If you also include their ideas in the changes, then they will feel themselves to be a valued part of the team. If you pace these changes correctly, you can stimulate 'multiple Hawthorne effects' and continually increase productivity. And notice, this is not slave driving. The increased productivity of a Hawthorne effect comes from the enthusiasm of the workforce; they actually want to work better.
A GENERAL APPROACH
In management there is always a distant tune playing in the background. Once you hear this tune, you will start humming it to yourself: in the shower, in the boardroom, on the way to work, when watching the sunrise. It is a simple tune which repeats again and again in every aspect of your managerial life; if goes:
PLAN - MONITOR - REVIEW
Before you start any activity you must STOP and THINK about it: what is the objective, how can it be achieved, what are the alternatives, who needs to be involved, what will it cost, is it worth doing? When you have a plan you should STOP and THINK about how to ensure that your plan is working. You must find ways of monitoring your progress, even if it is just setting deadlines for intermediate stages, or counting customer replies, or tracking the number of soggy biscuits which have to be thrown away, whatever: choose something which displays progress and establish a procedure to ensure that happens. But before you start, set a date on which you will STOP again and reTHINK your plan in the light of the evidence gathered from the monitoring.
Whenever you have something to do, consider not only the task but first the method. Thus if there is a meeting to decide the marketing slogan for the new product you should initially ignore anything to do with marketing slogans and decide: 1) how should the meeting be held, 2) who can usefully contribute, 3) how will ideas be best generated, 4) what criteria are involved in the decision, 5) is there a better way of achieving the same end, 6) etc. If you resolve these points first, all will be achieved far more smoothly. Many of these decisions do not have a single 'right' answer, the point is that they need to have 'an' answer so that the task is accomplished efficiently. It is the posing of the questions in the first place which will mark you out as a really great manager - the solutions are available to you through common sense.
Once the questions are posed, you can be creative. For instance, 'is there a better way of producing a new slogan?' could be answered by a quick internal competition within the company (answers on a postcard by tomorrow at noon) asking everybody in the company to contribute an idea first. This takes three minutes and a secretary to organise, it provides a quick buzz of excitement throughout the whole company, it refocuses everyone's mind on the new product and so celebrates its success, all staff feel some ownership of the project, and you start the meeting with several ideas either from which to select a winner or to use as triggers for further brainstorming. Thus with a simple -- pause -- from the helter-skelter of getting the next job done, and a moment's reflection, you can expedite the task and build team spirit throughout the entire company.
It is worth stressing the relative importance of the REVIEW. In an ideal world where managers are wise, information is unambiguous and always available, and the changes in life are never abrupt or large; it would be possible for you to sit down and to plan the strategy for your group. Unfortunately, managers are mortals, information is seldom complete and always inaccurate (or too much to assimilate), and the unexpected always arrives inconveniently. The situation is never seen in black and white but merely in a fog of various shades of grey. Your planning thus represents no more than the best guess you can make in the current situation; the review is when you interpret the results to deduce the emerging, successful strategy (which might not be the one you had expected). The review is not merely to fine-tune your plan, it is to evaluate the experiment and to incorporate the new, practical information which you have gathered into the creation of the next step forward; you should be prepared for radical changes.
LEADERSHIP
There is a basic problem with the style of leadership advocated in this article in that nearly every historic 'Leader' one can name has had a completely different approach; Machiavelli did not advocate being a caring Protector as a means of becoming a great leader but rather that a Prince ought to be happy with 'a reputation for being cruel in order to keep his subjects unified and loyal'. Your situation, however, is a little different. You do not have the power to execute, nor even to banish. The workforce is rapidly gaining in sophistication as the world grows more complex. You cannot effectively control through fear, so you must try another route. You could possibly gain compliance and rule your team through edict; but you would lose their input and experience, and gain only the burdens of greater decision making. You do not have the right environment to be a despot; you gain advantage by being a team leader.
A common mistake about the image of a manager is that they must be loud, flamboyant, and a great drinker or golfer or racket player or a great something social to draw people to them. This is wrong. In any company, if you look hard enough, you will find quiet modest people who manager teams with great personal success. If you are quiet and modest, fear not; all you need is to talk clearly to the people who matter (your team) and they will hear you.
The great managers are the ones who challenge the existing complacency and who are prepared to lead their teams forward towards a personal vision. They are the ones who recognise problems, seize opportunities, and create their own future. Ultimately, they are the ones who stop to think where they want to go and then have the shameless audacity to set out