Showing posts with label Projects. Show all posts
Showing posts with label Projects. Show all posts

Saturday, 24 September 2016

The Pen Is Mightier Than the Keyboard

Taking notes in long hand might sound a bit old school, in fact some of us were probably pretty good at it when we were in school. These days we probably go into a meeting with our tablet or laptop booted up and type away a summary of a meeting or update bullet points on a spreadsheet or email. If we have been put through a barrage of PowerPoint we may just request a copy of the presentation and use that as our notes. Scribbling notes on a foolscap page is literally a lifetime ago. That is not a good thing.

Several studies have looked at how note taking impacts on how we understand and retain information. One recent study by Princeton University looked specifically at how note taking using a laptop compared with long hand. The laptop note takers scored poorly and were associated with impaired learning and a reduced grasp of conceptual issues, when compared to their long hand counterparts. The shallower processing involved when we just retype what we hear compared to the more complex processing it takes to physically sketch and write notes is suspected to be at play here, or as psychologists call it, Levels of Processing Theory.

If you are hiring someone who will be customer facing, a business analyst or integration specialist, ask about how they take notes. A good note taker will be able to describe their own style, be that their own methods they have developed over the years, mind maps or something more formal (the Cornell Method).

Good note taking requires someone who can identify key words, is organised and can get into the flow of what is being discussed. These are all key skills if you are hiring someone to capture customer requirements, understand a business process or detail what was committed to in meetings.

If you do hire an analyst and are wondering how they are getting on, take a look at their notes. It could be a window into how organised and up to speed they are in their project work. As part of staff induction, splash out on a good pen and fancy jotter. It is not just a perk, it also reinforces the importance of note taking, by hand. If someone asks you for a copy of the presentation you just gave, you can assume they will recall very little of what was discussed. That may or may not be a good thing.




Monday, 1 August 2016

Bad at saying 'No'? That's a probem


I read a good article by Peter Bregman about how to say 'No'.

This is a very under-rated skill to have. Saying 'No' is vital to keeping work and customer expectations at manageable levels.Failing to say ‘No’ when we instinctively know that we may not be able to deliver is a bad move that can come back to bite us over and over. What ensues is usually a lengthy and awkward process of realigning customer expectations and eventually telling them ‘No’. In the meantime, you probably have damaged customer relationships, frustrated staff and wasted time figuring out how to limit the damage.

This happens quite a bit in software start-ups that code their own product. Feature creep can set in and it’s easy to say ‘Yes’ to an important client when they inevitably ask for a function or change request. At start-up phase pretty much any client is an important client.However, you will find yourself making promises you can’t keep, burning the candle at both ends (working late / weekends) to come good on commitments when you should have said ‘No’. That leads to endless firefighting where you neglect the basics of making sure your strategic business systems are running properly (sales pipeline, support documentation, credit control, cost benefit analysis of activity).

Key staff will get demotivated at constantly working under pressure or jumping from one ‘priority’ to another and probably leave (if you have more than three priorities, you don't have any). You will more than likely rehire in a hurry because you need someone straight away. Because you have taken your eye off the ball on the fundamentals of the business you may neglect your sales process, prospect call backs etc, so the clients that made the initial request now become even more important (as other sales haven't grown as planned ). It then gets even harder to say 'No' to their next change request. On and on it goes.

If you are a start-up company in firefighting mode or constantly find yourself avoiding calls from clients, end up working weekends, late at night, ask yourself how often you have said ‘No’ to a request in the last week. Chances are it’s not very often. There is nothing wrong with being busy and firefighting, just so long as it’s for a strategic or commercially sound reason. If it’s purely because you could not say ‘No’, then it’s a problem. 

As someone once said, 'The road to hell is paved with good intentions', failing to say 'No' might be just laying another stone on that road for your projects or organisation. 

Sunday, 2 November 2014

Why a bonus might be a bad idea

You have a business problem to solve or a new project to get live. In order to make sure your people deliver, you decide to offer a bonus, stock options or some other incentive to get the job done. This might be a really bad idea and here is why.

Way back in 1945 Karl Duncker had his candle problem experiment posthumously published. It was a task based on problem solving. Participants were given a candle, some matches and a box of tacks. They were then asked to fix the candle to a cork board on the wall. They needed to do it in such a way that when lit, the candle wouldn't drip wax on the table underneath the cork board.

The solution (spoiler alert), is to use the box holding the tacks as a candle holder, attach the box to the wall and put the candle in it. Most people solve this eventually but they solve it a lot quicker if the tacks are out of the box and the box is seen as a separate piece of equipment.

When the tacks were in the box the participants saw it only as a tack-box, not something they could use to solve the problem. This phenomenon is called ‘Functional fixedness’.

Sam Glucksberg added a very interesting step to this in his 1962 paper, “Influence of strength of drive on functional fixedness and perceptual recognition”. He decided to incentivise people to solve the candle problem. One group got money for solving the problem, the quicker they solved it, the more money they got. Another group were offered nothing, they were just asked to solve the problem.

When the tacks were presented outside the box (making the solution more obvious) the group that were incentivised out-performed the group that were paid nothing. This is what we would expect, rewarding results improved performance.

However, when the problem was presented in its more complex form with the tacks in the box, the incentivised group did significantly worse than the group paid nothing. Incentives killed performance and results. The bonus for getting it right back-fired big time. Participants with no financial incentive took 7:41 minutes to solve the problem, the people who were incentivised, took 11:08 minutes to solve the problem.

Glucksberg found that not only did the financial incentive make people slower at problem solving, the slowness increased with the incentive. The higher the monetary reward, the worse the performance. This was not a one off, the result has been replicated over and over in other experiments.

The key point is that incentives narrow our focus. When participants are incentivised, they can’t see the solution to the problem (the box holding the tacks). They think mechanically not creatively. Narrowing our focus inhibits this creative thinking and gets us straight into the task as we see it.

The lesson here is that if your employees have to do something straightforward, like putting regular parts together or following a specific instruction on an assembly line, financial incentives work well for these mechanical tasks.

However when we need do something that requires any creative or critical thinking, financial incentives damage performance. When we need to think out of the (candle) box, offering a financial incentive keeps our focus in the box. We don’t see the big picture and solutions prove more elusive.

For the types of jobs many people have in the 21st century knowledge economy, bonuses and incentives are a bad motivator. Worse than not getting results, they damage performance, it’s not that they don’t do any good, they actually do harm.

Giving a bonus to software developers to get a project delivered on time or Business Development Manager to get a new commercial product live or a Marketing Executive to hit a sales figure are all the types of tasks that Glucksberg and others have shown, suffer when people are incentivised.

This has been well documented and repeated since 1962 and yet pretty much ignored in most management strategies. It is a mistake that companies continue to make today, more than 50 years since Glucksbergs first publication. 

It could go some way in explaining the disastrous performance of our banks, which had a well embedded bonus culture in senior management, the guys who should have been watching the big picture. It may explain why many well-funded start-ups disappear shortly after venture capitalists arrive. Most VC funding involves the current management staying on for a while and the company or its share price hitting incentivised targets for set time period. The creative thinkers that set up and got the company going now have their creative thinking dimmed and their focus narrowed by VC penalties or bonuses.

The next time you offer or are offered a bonus think again. Fifty years of research suggests that you will lose sight of the big picture and your days of thinking outside the box could be over.


Daniel Pink has an excellent TED talk which covers this and is well worth a listen.

Tuesday, 9 September 2014

Shake it up - New faces help group creativity

We all know it’s good to shake it up a little every now and again, to introduce some new faces to different areas of the business or to assign people to new roles. We see it at government level in cabinet reshuffles, we even see it in sports teams where a few fresh faces gets the whole team playing differently.

I recently came across some research in this area from Hoon-Seok Choi at Sungkyunkwan University in South Korea and Leigh Thompson at Northwestern University, USA. They looked at how new faces impact on a groups level of creativity.

The study examined the creativity of 33 three-person groups across two tasks. The idea was very simple. After the first task, half the groups exchanged one of their team for a newcomer from another group. The other half of the groups kept the same personnel throughout. The first task got the groups to think of as many ways as possible to categorise 12 vegetables into subgroups (e.g. can be eaten raw vs. cannot be eaten raw). The second task asked the groups to think of as many uses as possible for a cardboard box.

There were no differences between the groups for the first task. They all came up with roughly the same number of sub groups for vegetables. However, when it came to the second task, the groups who swapped one of their members then went on to think of significantly more uses for a cardboard box, and significantly more different kinds of uses, than did the groups who’d kept the same members. Further analysis of the contributions made by each individual showed that the new guy on the team increased the creativity of the two original team members.

There could be downsides to this however. For example you could break up a well-balanced group, you could introduce personality conflicts or create leadership rivalries. Getting back to sport teams, you might see this go wrong when a manager tinkers too much with a winning team.


That aside, if you have a group that needs to be creative or innovative, try and mix it up a little. Fix any conflicts as they arise. Those fresh faces and new perspectives not only bring new inputs but also get the incumbents thinking more creatively. 

Tuesday, 15 July 2014

You Can Do It

Ever tried talking to your self when the going gets tough? Maybe you should. This technique known as ‘self talk’ has been shown to improve self control and boost morale. However when your back is to the wall, a deadline is hurdling towards you and the pressure is on, are you better off telling yourself ‘You can do it!’ or ‘I can do it!’?

The BPS reports on some worked done by Sanda Dolcos from the University of Illinois which seems to favour the ‘You’ approach. She got 95 psychology undergrads to imagine they were a character in a short story. The characters were presented with a number of choices and decisions to make. The students were asked to write out the advice they would give to themselves if they were in a similar situation. Half the participants were instructed to use the first-person "I" in their self-advice, the others to use the second-person "You". Once they had given their advice, the participants completed a series of anagrams. Those who'd given their fictional selves advice using "You" completed more anagrams than those who'd used the first person "I" (17.53 average completion rate vs. 15.96).

In a similar study, 135 students were asked to write down self-advice to encourage exercising more over the next two weeks. Those who referred to themselves as "You" in that advice subsequently stated that they planned to do more exercise over the next two weeks, and they also went on to report more positive attitudes towards exercising, than those students who referred to themselves as "I".


Referring to yourself as ‘You’ seems to be the way to go. One possible reason for this could be that it reminds us of receiving support and encouragement from others, especially in childhood. It may also be a little more assertive, as if you are ordering yourself to behave in a certain way.

Either way, when an awkward software bug lands on your desk or the boss drops a ridiculous presentation on you at short notice or your budget gets slashed, tell yourself ‘You can do it’. Maybe you can or maybe you can’t but however hard is, your chances may be improved. 

Sunday, 1 June 2014

Fading Memories

"Fading Affect Bias" (FAB) describes the way negative emotions fade quicker from memory than positive emotions. This happens when we experience something that we perceive as threatening, unpleasant, unpredictable or chaotic. Once we decide we don’t like something, our cognitive response is to forget it over time, unlike pleasant experiences, which we want to remember. The bad experiences gradually fade out, the good ones remain.

A study published in the journal ‘Memory’, found this to be cross cultural. The researchers organised 10 samples from different groups of people around the world. These included Ghanaian students and elderly German citizens (who were asked to recollect the fall of the Berlin Wall). In total, 562 people were included in the research.

The people participating in the study had to recall a number of events in their lives, both positive and negative. For each event, they rated the emotions that they felt at the time it happened, and then the emotions that they felt in the present when remembering that event.

The authors found that every cultural group included in the study experienced the FAB. In all of those sampled, negative emotions associated with remembered events faded to a greater degree than positive emotions did. Interestingly, there was no evidence that this effect changed with people’s age. The FAB is a lifelong cognitive bias, it affects young and old.

The conclusion is that our ability to look back on events with rose-tinted glasses might be important for our mental health, as it could help us to adapt and move on from adversity: It only makes sense to enjoy the positive benefits of pleasant experiences and to limit our potentially traumatic recall of unpleasant experiences. The authors suggest that the FAB is part of a set of cognitive processes that help emotional regulation and aid psychological resilience. 

From a work point of view, if you are reviewing past projects, sales initiatives or previous product launches, be mindful that some of the problems experienced at the time may have faded from memory.

If you want to know what went wrong, better check the written records and formal notes taken at the time. Chances are most of the people involved in the project will have a version of the truth coloured by the FAB which may not reflect what really happened. If you are involved in a project that did go wrong, get the facts on paper as early as possible, before the fading kicks in.

Sunday, 11 May 2014

We care about what we do - a Lego Lesson

Sometimes in work you can feel like a cog in a wheel, working away on your specific task, over and over again without ever seeing the finished product. This could be an admin assistant processing orders or marketing material or it could be a computer programmer writing server side functions for some application.

Dan Ariely, working with Harvard University has thought about this and asked the question, “Does Seeing the fruits of our labour may make us more productive?”

The researchers had participants build characters from Lego’s Bionicles series. All the participants were paid decreasing amounts for each subsequent Bionicle: $3 for the first one, $2.70 for the next one, and so on. However, one group’s creations were stored under the table and disassembled after the experiment. The other group’s Bionicles were disassembled as soon as they’d been built. They were built, taken apart and built again and again and again. “This was an endless cycle of them building and we destroying in front of their eyes,” Ariely says. This is not unlike Paul Newman digging and filling in the hole in the classic movie ‘Coolhand Luke’.

The results between the two groups were very interesting. The first group (who saw the end product which remained intact) made 11 Bionicles, on average, while the second group made only 7 before they quit (in case you are wondering Paul Newman quit digging the hole too).

The point here is that while reward did not differ i.e. one group were not paid more or had better working conditions or other motivational perks, seeing the fruits of their labour seemed to lead to greater productivity and a willingness to keep on going. Just being given the same task over and over with no tangible end product to look at, seemed to dull enthusiasm and results. You could speculate that this group may have felt that they were just assembling but not really creating anything.

The lesson here for the work place is that we may need to think of work as less of an assembly line where each person does their bit and instead give staff a chance to see what their contribution creates. That could be allowing admin staff to see marketing feedback or meet with clients and see the difference they make in getting a sale. It could be having the computer programmer seeing how safe, fast or easy their functions make the system for end users.

This could explain why some start ups find it easier to get staff to work long hours, take on multiple tasks, often with minimal additional financial reward. I’ve worked in a few start ups where this was the case. Perhaps in these scenarios, staff see the difference they make to the big picture, growing the company and building a product that end users enjoy. To paraphrase Ariely, “They see the fruits of their labour”.


Make some time for staff to see the point and end product of their work. Efficiency is more than figuring out ways to doing more stuff. How we think about our jobs and what works means to us plays a big part in motivation which in turn drives job satisfaction and productivity.

Thursday, 8 May 2014

Don't underestimate yourself


You may have read about the ‘Dunning Kruger Effect’ which outlines why incompetent people do not realise they are incompetent. Guess we could all think of a few people we've worked with that would fit into this theory.

There is however another scenario, the ‘Worse than Average Effect’. The idea here is that when we are good at something we assume other people are good at it too. We don’t give ourselves the credit for being particularly good at complex tasks and can even assume that loads of other people are probably better than we are.

A study from J Kruger found that we can underestimate our ability  for something difficult like playing chess, telling jokes or computer programming. At the same time we overestimate our ability at seemingly easier tasks like using a mouse or riding a bike.

The take away here is that when it comes to staff self reporting their ability on tasks or project work, take into account a possible tendency to underestimate how good they may be at the more complex items such as system design or process management and over estimate how good they are easier tasks like logging time records, drafting project plans, organising meetings. 

Saturday, 19 April 2014

The Pomodoro Technique

We all have things to do that we’d prefer to avoid or just don’t enjoy doing. This could be something monotonous, something that stresses us out or a task that is hard to do.

I recently came across a system called the Pomodoro Technique
. It is a time management technique developed by Francesco Cirillo in the late 1980s. It is named after a kitchen timer called a "pomodoro" and the idea is pretty simple. You set a timer for 25 minutes of work, then take a five minute break, then set the timer again. Every 4 sessions you take a longer break for 15 to 30 minutes. No matter how bad your task is, there are very few things we can’t do for 25 minutes.

The method is based on the idea that frequent breaks can improve mental agility and as work sessions are accomplished, you feel more in control and you can see tangible progress. The more in control you feel, the less stressed you feel and the quality of the work may even improve.

If you accurately record what you get done in 25 minutes that will help future planning and show up those hidden items that can take a bit longer than we expect.

I've seen this used in software development where two programmers work together on a screen review. That is a pretty open ended task but the defined sessions focuses the minds and charts progress. This also works with the idea that to solve any problem, you start by reducing it to achievable individual tasks and get each one done one by one.

Try it out and see if it works for you, at the very least you will get regular breaks and have a more accurate record of your efforts.


Wednesday, 20 November 2013

The No Empathy Sandwich


Having worked in software for a number of years I often noticed how my workload seemed to accumulate almost from no where (I use that term deliberately). I’d find myself with multiple ‘mini’ projects on the go, tight deadlines and a fair amount of pressure. I’d sit back and wonder ‘how it came to this?’. The answer could usually be traced back to a conversation about a proposal, change request or upgrade where I agreed to take on something that in hindsight was not a good idea. It was driven by a reluctance to say ‘No’.

Where this reluctance came from, I’m not quite sure. I worked in a few start-ups where nothing was impossible, crazy deadlines and late nights were par for the course. Saying ‘No’ was not part of the culture in that environment and the customer was literally always right. Not saying ‘No’ and always acceding to customer demands, can lead to a situation where your customers run your business, not you. That is not a good thing, even in start-ups. Product road-maps get hi-jacked, innovation suffers at the expense of piecemeal tweaking and delivery.

So assuming saying ‘No’ needs to be done every now and again, is there a good or bad way of delivering the potentially bad news? Turns out there is.

I came across a neat article which explained it in an equation called the ‘Empathy Sandwich’ as “No= Empathize + Decline + Empathize Again”. For example a client says  ‘Can you add a new screen to report on XYZ?, it takes me ages to do it manually‘ . First comes a little bit of empathy ‘Ok , I see where you are coming from, it’s not easy to get time for that every week’. But then comes the Decline – ‘But I don’t have a project team I could put on that change‘. Followed up by some more empathy  ‘I hope your workload levels out, you guys do a really great job over there’.

That example might sound a touch contrived but you get the point. Saying ‘No’ in a way that shows some consideration and understanding beats a dismissive tone and helps keep the relationship going, despite the refusal.

By saying ‘No’ you will free up more time, finish more projects, deliver higher quality work and end up fire-fighting a lot less. That will make for happier customers in the long term as you can focus on innovative product development, meet the deadlines you do commit to and not get pulled between multiple piecemeal requests. You will be happier too. Who could say ‘No’ to that?




Thursday, 8 August 2013

Beware of the guy with nothing to lose


I recently read a post by Alex Fradera at the BPS Occupational Digest which looked into how two different types of employees working in the same organisation would respond to change. One employee was well paid, felt valued and had an attentive boss. The other was poorly paid, under valued and disconnected from their boss.

If change was being introduced to the organisation you might expect the happier employee to be more resistive, as they have more to lose. It turns out that research specifically asking this question suggests that the better you are treated, the more open you are to change, even though you have most to lose.

The better employees felt they were treated, the less anxious they became. They had good reason to expect that if they were treated well before the change, they would continue to be treated well afterwards. The employee treated badly is already in a mind-set where they expect to be taken advantage of and the forthcoming change agenda was just another way for that to happen.

I was surprised by this, I had assumed that those with most to lose would be most anxious about losing their current cushy number. Then I thought about a large multi national insurance company I had worked in where there was a merger and major departmental changes.

The overriding feeling at the time was uncertainty as to how individual roles would turn out. We were reassured by management euphemisms about synergies and stability. Not being completely naïve, my colleagues and I viewed this as spin and PR, the real proof would come once the change was implemented. The feeling of uncertainty came down to trust, did we trust what we were being told?

This could be at play in the research cited by Alex Fradera. The person treated well probably trusts the employer and their change agenda, the other guy is probably very cynical and has no reason to believe that the change will lead to any good. It just means even more hassle.

So if you are changing how things work, watch out for those with nothing to lose, they could be the most resistive. If you want the change to go a little smoother, make an extra effort so that staff feel valued beforehand.
 

Sunday, 12 May 2013

Crazy Deadlines good for Creativity?

So does a deadline help deliver creative solutions? I once worked with a colleague who always felt he needed a deadline to get things done, that kicked off the ‘backs to the wall’, ‘consider anything’ type of thinking that worked for him.

I came to realise over the years however that this guy was a procrastinator and it was the deadline shaking him out of his procrastinating routine that delivered for him. It wasn’t that the deadline made him anymore creative, it just got him focused on the job. That guy probably thought that serious time pressure was the only way to get resourceful when it came to delivering, because he had never actually tried it any other way.

I recently read an article on the Harvard Business Review by Teresa M. Amabile, Constance N. Hadley, and Steven J. Kramer which directly addressed the question of whether a deadline helps creativity.

The paper uses a case study from a software developer who was set an impossible deadline to deliver a complex specification that required coming up with creative solutions under very tight deadlines. Anyone who was worked in software development will identify with this. The industry has a long history of the time needed to complete complex work being underestimated, with dire consequences for those involved (never mind the software produced).

The summary from their research is that on days of the most extreme time pressure, the people involved were 45 percent less likely to come up with a new idea or solve a complex problem. Even worse, there was a kind of “pressure hangover,” with lower creativity persisting for two days or more.

According to Amabile and colleagues, ‘working under the gun’ as they put it, is a bad idea when complex, creative thinking is needed. I agree and I know plenty other software developers who have been there and would concur.

Thursday, 2 May 2013

The most urgent decisions might not be the most important ones

I read a really good post recently on time management. It put forward the idea of The Eisenhower Matrix. This is based on the notion that the most urgent decisions are rarely the most important ones.
You may go into work  this morning with your tasks for the day mapped out, calls to make, meetings to attend. A few problems or decisions then cross your desk or inbox. You start reacting to whoever is shouting the loudest (hopefully just in the figurative sense). It is very easy to start doing the most urgent responses straight away. The end result may be that you do not allocate enough time (or in a really bad case forget) to deal with the most important tasks.
I've seen this happen quite a bit in software development where developers/project managers get urgent calls to fix bugs or make product changes. The rationale was often, 'we need to do this to win or keep a customer'. The important job of making sure you have a stable code base, that changes are peer reviewed, that the product development is driven by strategy not client whims can get ignored or put to one side. There is no deliberate decision made to drop the important aspects of the software development process, it just happens. The important stuff like version control and scheduled upgrades get left behind.
So if something does cross your inbox, figure out if it is urgent or important or both. Use the Eisenhower Matrix to figure out when to do it or who to delegate it to. You may have a little more time on your hands and get to make those important decisions at the right time. By getting the important decision right, in the long term you should have less urgent items landing as surprises in your inbox.

Saturday, 27 April 2013

If something happens, then you need a plan

We all do a bit of project planning every now and again. This can be for a formal large project with multiple goals and participants or a plan just to get an email put together and sent off.

Research by Gollwitzer etc al, 2006 suggests that we need to anticipate problems and set a series of ‘if then’ actions. This would be if the new piece of software is not live by an agreed date, then, we have a paper based system to use in the short term. In other words we look at what can go wrong, what can be outside of our control and develop contingency plans that are worked out in detail and ready to go.

When the inevitable does occur and some original deadline or action does not materialise, we are not left floundering, wondering what we can do about it or who do we call. Your ‘if then’ is ready to swing into action, you continue to feel in control. You stay in business.

This sounds like really basic advice and a really obvious thing to do. You would however be surprised by the number of people out there who are happy to wing it and not do this extra level of planning.
Once they come up with a plan they let it at that and treat the ‘if thens’ with a touch of ‘we’ll cross that bridge when we come to it’. That type of head in the sand thinking can be a serious threat to your business.
While you can't have an 'if then' for every project milestone, you could have them for the milestones that are an operational threat. I have seen clients unable to issue monthly invoices with devastating implications for cash flow because a data load into a new billing system hit a technical snag. This is particularly important for projects with several suppliers. When something does go wrong, each will point the finger at the other and cooperation to resolve the issue could be in short supply.
So review your project plan. Identify the junctures where failure will seriously jeopardise your organisation and put in your 'if then' plans for these. You will keep a degree of control and not be left at the mercy of suppliers and project managers. Always have an option open, if the worst then happens, you will be ok.

Monday, 8 April 2013

Be careful what you visualize

We have all heard of visualizing our goals. There are examples of football place kickers visualizing getting the last minute winner. Many golfers have visualized sinking that winning putt.

Research by Pham and Taylor at the University of California, suggests however that visualizing needs to involve the process of achieving your goal, not just the outcome. In other words, you visualize your run up to the ball, feet position, momentum, the contact with the ball, the release of the strike on the ball. Just visualizing the ball going between the posts is not enough.

Thinking about the process, in detail and ‘experiencing’ it via visualization helps us to focus the mind on potential problems, what needs to be right, what can go wrong and how to overcome any problems.

Just visualizing the outcome lets us prone to the ‘Planning Fallacy’ This is a cognitive error which affects most of us, regardless of experience. We continually fail to anticipate just how much of any plan can and will go wrong. We are hardwired to think everything will be much easier than it really will be.

In the research cited, students were asked to either visualize their ultimate goal of doing well in an exam or the steps they would take to reach that goal, i.e. studying.

The results were clear-cut. Participants who visualized themselves reading and gaining the required skills and knowledge, spent longer actually studying and got better grades in the exam.

Just imagining reaching a goal may be worse than ineffective, it may reduce our performance. In the study by Pham and Taylor, participants who just envisioned a successful outcome studied less and actually had reduced motivation.

So for visualization, like the song goes, “it ain’t what you do it’s the way that you do it”.



 

Sunday, 17 February 2013

It Costs Big if you can't say 'No'

I read a good article recently on Psychology Today by Peter Bregman about how to say 'No'.
This is a very under-rated skill to have. Saying 'No' is vital to keeping work and customer expectations at manageable levels. I have been guilty in the past, of failing to say ‘No’ when I knew immediately it was the right answer in the long term. What ensues is usually a lengthy and awkward process of realigning customer expectations and eventually telling them ‘No’. In the meantime, you probably have damaged customer relationships and wasted time figuring out how to get the message across.
This happens quite a bit in software start-ups that code their own product. Release versions and source code control run a little loose and it’s easy to say ‘Yes’ to an important client when they inevitably ask for a function or change request. At start-up phase pretty much any client is an important client.
However, you will find yourself making promises you can’t keep, burning the candle at both ends (working late / weekends) to come good on commitments when you should have said ‘No’. That leads to endless firefighting where you neglect the basics of making sure your strategic business systems are running properly (sales pipeline, support documentation, credit control, cost benefit analysis of activity).
Key staff will get frustrated at constantly working under pressure or jumping from one ‘priority’ to another and probably leave. You will more than likely rehire in a hurry because you need someone straight away. Because you have taken your eye off the ball on the fundamentals of the business you may neglect your sales process, prospect call backs etc, so the clients that made the initial request now become even more important (as other sales haven't grown as planned ). It then gets even harder to say 'No' to their next change request. On and on it goes.
If you are a start-up company in firefighting mode or constantly find yourself avoiding calls from clients, end up working weekends, late at night, ask yourself how often you have said ‘No’ to a request in the last week. Chances are it’s not very often. There is nothing wrong with being busy and firefighting, just so long as it’s for a strategic or commercially sound reason. If it’s purely because you could not say ‘No’, then it’s a problem

Saturday, 12 January 2013

Assumptions at Work

Much of our recent national and economic history can be traced back to not challenging assumptions. The assumption that house prices would keep on rising, endless access to cheap credit, that we would always earn more and more, that our banks and planners were well regulated. However don’t feel too bad about that, clinging to assumptions is part of human nature. The following is based on an article by Michael Michalko where he explains how assumptions work.
To understand how powerful and subtle assumptions can be, try doing this exercise in your head. Add up the following numbers as quickly as you can. Take 1000 and add 40 to it. Now add another 1000. Now add 30. Add another 1000. Now add 20. Now add another 1000. Now add 10. What is the total?
Our confidence in our ability to add according to the way we were taught in base ten at school encourages us to process the information in a certain way and assume an answer. If your total is 5,000, then you are wrong. 96% of people who add these simple numbers get the wrong answer. The numbers are arranged in such a way to set people up to get the wrong answer when adding using base ten. The correct answer is 4,100.Human nature is such that when we assume we know how to do something, we perform the act without much thought about the assumptions we make.
You have probably seen it in work or at home in household chores where people have particular ways of doing things. Once we think we know how something should be done, we keep doing it, then we teach others to do it the same way, and they in turn teach others until eventually you reach a point where no one remembers why something is done a certain way but we keep doing it anyway. We tend to accept whatever explanation someone with experience tells us. They have done it for years and so know best.
If you work in a job where mentoring is part of induction or continuous training ask yourself ‘why’ every now and again and see if you know the answer. Unfortunately we don’t ask that all important ‘why’ often enough and slip into the habit of not challenging assumptions.
This is well demonstrated in an experiment psychologists performed some years ago. It began with a cage containing five monkeys. Inside the cage, they hung a banana on a string with a set of stairs placed under it. Before long, a monkey went to the stairs and started to climb towards the banana. As soon as he started up the stairs, the psychologists sprayed all of the other monkeys with ice cold water. After a while, another monkey made an attempt to obtain the banana.  As soon as his foot touched the stairs, all of the other monkeys were sprayed with ice cold water. Bit of conditioned learning kicked in here. It's wasn't long before all of the other monkeys would physically prevent any monkey from climbing the stairs.
Now, the psychologists shut off the cold water, removed one monkey from the cage and replaced it with a new one. The new monkey saw the banana and started to climb the stairs. To his surprise and horror, all of the other monkeys attacked him.  After another attempt and attack, he discovered that if he tried to climb the stairs, he would be assaulted. Next they removed another of the original five monkeys and replaced it with a new one. The newcomer went to the stairs and was attacked. The previous newcomer took part in the punishment with great gusto. In turn, they replaced a third original monkey with a new one, then a fourth, then the fifth. Every time the newest monkey tried to climb the stairs, he was attacked.
The monkeys had no idea why they were not permitted to climb the stairs or why they were beating any monkey that tried. After replacing all the original monkeys, none of the remaining monkeys had ever been sprayed with cold water. Nevertheless, no monkey ever again approached the stairs to try for the banana. Why not? Because as far as they know that's the way it's always been around here. 
We do the same in the workplace. How many times have you heard "It has always been done this way” or “Don't mess with what works." Instead of challenging these assumptions, many of us, like the monkeys, simply keep reproducing what has been done before. It's the easiest thing to do. Just like adding using base ten.
This also sheds some light on why change is sometimes very difficult, we are making assumptions even when we don’t realise it and breaking that cycle of behavior is difficult both personally and at a social / corporate level. It may even explain why for years we assumed the church, politicians were to be trusted, ‘sure we’ve always trusted them’. Next time you notice yourself making an assumption, do yourself a favor and challenge it. Don’t be a monkey, your reward could be that dangling banana everyone else said you couldn’t have.

Saturday, 5 January 2013

Beware of the "Quiet Fixers"

Does your company have a culture of "Quiet Fixers"? This when a problem arises, someone notices, applies some fix or correction and moves on with minimal disruption to anything else.

It does not sound too bad until you think about it for a minute. Mistakes often have side affects that cause another problem else where, or the fix might not be addressing the root problem. The Quiet Fixer could be just sowing the seeds for future reoccurance of the same mistake or a worse one somewhere else.

In a Harvard Business Review interview, former Toyota chairman Katsuaki Watanabe stated, "Hidden problems are the ones that become serious threats eventually. If problems are revealed for everyone to see, I will feel reassured. Because once problems have been visualized, even if our people didn't notice them earlier, they will rack their brains to find solutions to them."

In Toyota, if a problem is noticed, production on the line stops, the entire team comes together to identify the root cause of the problem, to ensure that it does not happen again. This can be noisy and a little heated, but it leads to better quality and productivity in the long term.

I have seen Quiet Fixers in most places I have worked, particularly in software development where a bug is fixed and verified, but the root cause of why a bug was developed in the first place in not addressed. This was often poor business analysis, project management, choice of technologies, almost always nothing to do with the guys writing the actual code. Invariably the problem raised its head again and again in many different projects.

Quiet Fixers can also inhibit learning as we don't get the chance to know about parts of the organisation or process that we are not directly involved in. By going after the root cause of a problem, you will find out things about how you work that will surprise you and hopefully allow you to plug any process or communication gaps that inevitably exist.

So beware of the Quiet Fixers and try to develop a culture of Loud Fixers. It might seem a little disruptive or awkward at the outset, but it can lend itself to better quality, improved learning and more stable productivity in the long term.

Tuesday, 30 October 2012

BREAKING: Have you too many alerts?

Over the years I have been involved in the design and implementation of various computer applications.

When installing a system we were often asked to make screen changes to highlight certain situations. These included new or additional alerts for tasks that were over due, adding scrolling text about some process already underway or putting in pop ups to remind staff of best practice.

More often than not these requests were declined, because if they were implemented, they would have resulted in a very busy computer screen for the end user.  'Alert Fatigue' would creep in. This would result in sending alerts that would be irrelevant for many, and worse than that, when people get enough of these, the alerts that are actually important would be ignored.

I recently came across some research that seemed to agree with the philosophy of being miserly when it came to adding alerts, scrollers etc to screens. An experiment by Lori Bergen, Tom Grimes and Deborah Potter had college students watch CNN Headline News. Some students watched the regular news, complete with all the on screen extras such as flashing icons, the stock quotes, breaking news and the rolling messages that scroll along the bottom of the screen. Other students watched the same news, but with the extras edited out, they just saw the basic screen.

Students that watched the busier screen with all the alerts and extra text did far worse in recalling facts than those who watched the basic news screen.

The lesson here for the workplace is that we can now have plugins and pop ups for many applications on our desktops or smart phones. We have our Google or Yahoo pulling in the news, weather, stock prices as we read our email. The bottom right hand corner of your PC screen will have pop ups for scanning email, Instant Messaging, Skype activity, Calendar Events.

Like the participants in the experiment, our ability to absorb the key facts of what we are actually doing or looking at on our screens may be affected. If you work in a job where attention to detail and recall of facts are important, then perhaps you should review the desktop or apps on your PC.

Have a look at the alerts and notices that do pop up, consider how important they are. Are they 'clutter' or actually helping you to work more efficiently. If they are on the 'clutter' end of the spectrum, then a spring clean of your apps and desktop icons may be in order.

There is also a lesson here for website design and on line marketing. Flashing ads, visit counters, social media feeds, pop ups asking for surveys are all easy to put on, but if you want people to recall what is on your website, then you may need to cut back on these and be more circumspect about adding new features in the future.

Sunday, 21 October 2012

Anchoring & Estimates

I was in a meeting recently discussing a sale between two software systems and a potential large client. Integration between the two systems came up. It was a high level discussion as the project is not funded yet. Even though it was still at 'Pre-Sales' stage, the client was looking for an estimate on how much effort (and cost) would be involved in the integration aspect.

Without substantial analysis, it is hard to give an estimate and there is no time or funding to do the analysis, so you have a bit of a  chicken and an egg. A sale being a sale, both software companies did not want to over complicate the situation and embark on time consuming pre-project work. If they did, the deal would in all likelihood fall through.

One software company said they thought it was about 3 days work for them, the second company then came up with 5 days as their estimate.

I was talking afterwards to the person who put forward the 5 day estimate and asked him how he came up with that. "Well when the other guys were doing 3 days and we have to do a little bit more, 5 seemed reasonable, it would have created doubt if we said we don’t know".

This is classic Anchoring Bias, one of several cognitive biases that have been covered in many studies. Psychologists describe it as a human tendency to rely too heavily, or "anchor," on one piece of information when making decisions. An example of this in a business context would be an investor judging a stock price as overvalued or undervalued based on the stock's previous high price. The previous high price is the anchor. It is part of the larger study of judgement and decision making under uncertainty which is best exemplified by the work of  Daniel Kahneman and Amos Tversky.

The scenario above happens all the time, be it people being asked to give sales estimates, costs of production, number of people needed, or time lines for a project conclusion.

Where well analysed, firm evidence is lacking or suspect (as is often the case) then someone usually gives a ‘Guesstimate’ and this becomes the figure around which all other estimates are given. The origin of the guesstimate is often how long a similar task took or costed previously. Bold and convincing arguments are then needed to dislodge the guesstimate. Think back to a few meetings you have been in and you will recognise this.

So what can this mean for you in your work place? Well, one implication is that if you are going into a meeting where you know estimates will be required, get your estimate in first and let that dictate the pace, otherwise you will have to dislodge someone else’s anchor and that is easier said than done. If you understand the sports cliché 'get your retaliation in first'  you get the idea.

If you want to deliberately control the anchoring of any figures, then look at the agenda, speaking order, seating order, content of your presentation etc as a medium for setting out your numbers. If you can't prevent a number being anchored by some one else, be ready with a suggestion to have it bottomed out in another meeting or some other process. Letting it happen by accident is not good enough.

Getting back to my opening account, the second software company will now find it very difficult to charge for more than 5 days work, will really have to justify it if they do .That is not a position a project manager wants to be in.