Tag: Organisations

Posted on

The New Day: How Should I Think About My Failures?

Gratitude Attitude 2017 #22

Everyone wants to be a success. I have never met anyone who purposely set out to be a failure. Undoubtedly, this is why so much has been written on the topic “How to be a Success” and why these books are so popular.

However, The New Day daily newspaper closed just nine weeks after launching, Trinity Mirror confirms.

The New Day was a British compact daily newspaper published by Trinity Mirror, launched on 29 February 2016. It was aimed at a middle-aged female audience and was politically neutral. The editor, Alison Phillips, intended readers to get through the newspaper in under 30 minutes.

The new paper was initially available for 25p for two weeks, then rising to 50p.  Two million copies of the New Day was  given away on the first day, as the turquoise-branded upstart attempted to spark a revival in readership and gain ground against the mid-market Mail and Express offline.

Arrogance about their own ability to rescue a situation can prevent leaders from changing course

The New Day had no leading articles, no website, and columnists  and believed it could successfully  drag readers back to print?  The sad truth is that it did not attract enough attention and  failed to create  a daily newspaper that could  co-exist in the  digital age, especially as tabloids and broadsheets continue to  suffer a significant circulation decline.

ChwW9VfXEAAXh8e

Shareholders at Trinity Mirror’s annual meeting called the failure “demoralising”. Analysts said it was “embarrassing”.

Assume for a moment that the leaders of The New Day  had no idea  about the changes swamping the print media as a result of the digital revolution,  and carelessly  decided to invest  millions into the venture without undertaking a risk assessment and  also decided to  ignore every indication that the paper was failing.  That would have been embarrassing and demoralising.

However, the leaders decided to fail quickly and  shut down the project they  started.

Abandonment is a rare, difficult and a valuable management skill. The natural instinct of most people is to persist, particularly  when the project is a collective commitment, as most corporate ventures are,  but then  it becomes even harder to hit the red “stop” button.

The New Day’s editor, Alison Phillips, said in a statement posted on Facebook that the team “tried everything we could” but were unable to reach the figures needed to make it work financially.

We dread failure. We don’t like talking about it. Some of us will internalise and rethink our failures in our heads time and time again. Others will swipe them away, moving onto the next thing immediately. In the public, we prefer sweeping our failures under the rug, silently, while nobody is watching.

While this might save our feelings momentarily, this is not the way learn and innovate.

the new day

According to Albert Savoia – ex Googler and innovation expert,  most project innovations will fail.

“Most New Things Will Fail – Even If They Are Flawlessly Executed.” – Albert Savoia – Ex Googler

Does this mean you should stay away from trying new things (and failing in the process)? Certainly not. It just means you need to accept failure will inevitably be a part of the process.

In most cases, however, a combination of arrogance about personal ability to rescue the situation and blindness to the lengthening odds of success stops  leaders from changing course.

The natural lifespan of most projects is finite, and the rarities are companies that survive.

The Art of “strategic Quitting” Will Become More Important as Careers Fragment and Companies Exert More Discipline

So if an idea is doomed, organisations usually treat the person who pulled the plug  early on as a hero right? Not exactly, it’s complicated.

Roy Greenslade, Professor of Journalism at City University London, wrote a report in The Guardian explaining how The New Day had failed. He pinpointed the error of marketing a newspaper to people who inherently despise  newspapers, and the short period of time  between the announcement and launch, leaving  no  time to advertise the product. It was also published early in the evening  thus missing out on late-night breaking news such as Leicester City F.C.’s shock win of the Premier League.

“Nothing so powerfully concentrates a man’s mind on innovation as the knowledge that the present product or service will be abandoned in the foreseeable future.” – Peter Drucker

The first thing the Bible wants to say is that all of us have failed. None is without failure. If you think you haven’t failed, two things are true of you. One is you are blind to your failures and the other is you probably haven’t taken enough risks to try enough hard things so that you would be aware of your failures.

Peter Drucker’s influence on business management is legendary.  Peter  realised  that “systematic abandonment”   a regular, unsentimental spring-clean is critical to the fostering of new business ideas.

Conclusion,  every organization needs to have a regular “rummage sale” to determine which products, services, and programs are worth keeping and which ones must be abandoned.

 

Posted on

Taking the Right Path to Good Agile Implementations

1) A Wise Man Said Only Fools Rush In

Companies that goes nuts for agile because they know they have to deliver faster and for less cost to keep up with competitors may be making a big mistake and face a collapse of their efforts.

If they focused first on a deep understanding of their business’ needs, they could more accurately decide if agile is a good fit. A better approach for you to take is analyse your current processes  to determine if agile methodologies actually support your goals and needs.

2) Educated Stakeholders Make Excellent Allies

Agile works from a focal point of improving quality delivery and frequency. It does not start with reducing time to market or cutting costs. Those benefits are a result of implementing agile methods over time, after the requisite investment of time and resources has been made.

3) Don’t Do the Project Without at Least One Committed Product “Owner”

A “product owner” is a the committed business leader who will make or break the project. This person will be expected to put at least half of their time into the project. They’ll also be responsible for getting all the decisions made through the right channels in a reasonable period of time. You must have a leader like this to succeed.

4) Gain Consensus on the Definition Of “Finished”

Everybody on-board needs to agree on what constitutes being finished with any stage of implementation. For some, it will mean that by the end of each and every iteration, the production-ready software will be available. This is not always possible, so get out ahead of a potential problem and gain consensus.

5) Build an Exceptional Cross-Functional Team

Cross-functionality is what separates the ineffective agile teams from the high-performance ones. Team members have to be proficient in performing any and all necessary tasks so that they’ll be able to always deliver what the customers need.

Team building requires that you identify the right parties and that you shape them into a functional team by making sure that they share your own true goal of always delivering massive value to product owners.

6) Make the Proper Investment in the Tools That Support Agile

The beginning stages of any agile project will involve you investing in the  of the robust frameworks, infrastructure, and process automation tools that fully support agility. This includes a wide range of solutions like continuous build servers, automation testing, video conferencing, interactive chat, and software frameworks. Don’t scrimp on other important details like the solution architecture, either.

7) Retrospectives Need to Be a Main Priority

Inspection and adapting are the keys to agile. Organisations using this methodology use a vehicle called “retrospectives” to ensure these tasks are being performed correctly. A proper retrospective should embrace the qualities of self-improvement and transparency. Any actions that are a result of the retrospective must be given the highest priority. This is especially true of estimations, which are crucial to achieving the kind of team velocity that keeps projects on track.

8) Start the Project with a Solution Architecture

Even though documentation is not always the most glamorous part of any project, you’ll be well served to make sure you understand that documentation is still important to a successful project. Using a solution architecture pays off because it serves a blueprint for the final project that will be delivered by the team. Team members need this document so they understand what will happen if they make changes. Members who are added to the project at later days will use the documentation as a reference point so they can be brought up to speed.

9) Embrace the Fact That Change Is Coming and Plan for It

You can’t make a change without a cost in agile. Change is something you always have to embrace philosophically, but be aware of the costs and the impacts to the project. When you are doing the estimation process, factor in potential changes when applicable.

10) You and Your External Partners Should Have an Agile Relationship

Agile is not always the best fit for traditional vendors. They prefer contracts that use fixed prices and fixed outcomes. When you switch to agile you’ll need to make a point out of understanding the ramifications the changes will have with your vendors. You and they may have to make some changes to keep the relationship running smooth.

Try to build a transparent relationship with all of your external vendors. Risk Reward contracts that employ clearly defined KPIs work amazingly well for agile organisations.

Posted on

The Good, the Bad and the Ugly of Agile Methodologies

The Good, the Bad and the Ugly of Agile Methodologies

The “agile” buzzword has really taken hold among a myriad organisations worldwide. That result is not particularly surprising. Who wouldn’t love to employ light and fast tactics that allow them to respond to rapidly changing challenges? Despite all the optimism about agile methods, the bigger question is how well companies are actually doing when it comes to employing these methodologies in the real world. Without understanding what the core objectives of embracing agile methods are, it’s not going to be easy to gain results.

Agile methodology is employed in order to reduce the time, risk, and cost that is associated with a project. However, these massive benefits are not going to materialise out of thin air. They are the result of the dedicated work of a team who is well versed in implementing the methodology.

To become “agile” will require organisations to take a quantum leap in their culture. They will have to embrace the entire philosophy behind these methods or no real change will take place. Truly agile companies are the ones that have gone through a transformative process in order to implement brand new processes that say goodbye to the past. This takes a lot of work and effort and not all organisations are willing or able to do this.

Ugly Agile Implementations

Project teams that are solely focused on results and who don’t do their homework end up with very ugly agile implementations. These teams are so excited about agile as a concept that they convert everyone in their organisation into adopting the methods. The problem is, they do not spend the requisite time getting everyone on board with exactly what needs to be done.

Because of this oversight, the projects are plagued with poor communications and engagement. The project team and others in the organisation are each working on their own tasks with no thought to how the pieces fit together in the “big picture.” This is a major problem because agile methods really only shine when the whole organisation works as one well-oiled unit. In this scenario, major issues at the core of the project are neglected and the entire project goes off the rails. This leaves a bad taste in the mouths of managers, who are no longer excited about agile methods.

Really ugly agile implementations have the wrong focus. Because of this myopia, the true benefits of agile employment are never realised. Before long, things, unfortunately, go back to “normal.”

Bad Agile Implementations

Some businesses completely miss the boat when it comes to agile deployment. They’re interested in receiving the benefits of reduced costs, faster time to market, and cutting “red tape.” Despite this knowledge, they’re not truly committed to the all of the values that are espoused by the Agile Manifesto. Without this commitment, they cannot possibly hope to fully embrace a functional implementation.

Organisations like to invest in education and communications, but they ignore important concepts like utilising the tools that help them truly embrace agility. They even form teams that understand cross-functionality, but without empowerment they are unable to make vital decisions.

Lastly, organisations that do poor agile implementations perform project reviews regularly enough, but the input from the meetings is never acted on by anyone. The key issues that are preventing proper implementation are never properly addressed and the project fails on its promise. Organisation members swear off the agile methods forever at this point.

Good Agile Implementations

When business personnel and IT staff work together, good implementations of agile are the result. These units work together so that a project delivery methodology is presented to the organisation that meets its needs. They also spend the time to create the cultural changes needed to ensure the methods are successful.

In organisations like this, team members, business end users, along with senior management and key stakeholders received a continuous education that empowers them all. Cross-functional teams that excel are the results. These organisations also invest in the techniques and tools that fully support agile. That includes test driven development, continuous builds, new standards, and more. With these in place, a platform that ensures long-term success will be installed.

Particularly telling, these businesses conduct regular project reviews which they conceptualise as opportunities to improve instead of something that simply has to be done. When change is needed, they embrace it and plan for it. When it arrives, they are ready and the organisation continues to excel. A sign of a good agile implementation is when the organisation is  commits to making long-term changes that will benefit the methodology in the long run.

It doesn’t pay to underestimate just how difficult implementing good agile really is. Since major internal changes to how project delivery is done need to be embraced, the road ends up being a challenging one. Traditional managers will be challenged because empowered teams now have more input than ever before.

Once a good agile implementation is in place, the benefits are obvious and plentiful. An energised, cross-functional community of empowering people who are all focused on common goals get more done than ever before. Good implementation put platforms into use that improve project delivery because they allow for test-driven development, continuous integration, standards implementation, and best practice design applications.

Posted on

Top 10 Project Management Myths Debunked

Since the dawn of time, mankind has used myths to make sense of the uncertainty that surrounds us.  In the early 1990s  a lot of  people believed that project management was the best kept secret in business.  However,  because project management was not  seen as a  prevailing profession at that time, it suffered from a lack of awareness  which was  in a sense, a double edged sword. Those who were knowledgeable in the practice of project management became extreamly valuable to organisations and pioneers for  the profession.

These early adopters were able to convince organisations that project management practitioners were needed.  Myths around project management began to form in the business community  and as the role of the  project manager was unclear, questions were raised as to what project management was  and what it could offer organisations.

The definition of the word myth is a “widely held, but false belief or idea.” Here, we’re going to examine 10 of the most pervasive PM myths that have emerged.

Myth #1 – Contingency pool is  redundant  

This is one of the most ‘mythical’ myths that has plagued the industry  for a long time. Coupled  with the tendency to presume that ‘real work’ is tantamount to implementation or building something concrete and you have the perfect recipe for project disaster.  The thought pattern behind this approach typically originates from budget constraints and/or having unrealistic expectations. As we all know, or should know, the unexpected happens quite regularly. An effective contingency plan is important as it aims to protect that which has value (e.g., data), prevent or minimise disruption (e.g., product lifecycle), and provide post-event feedback for analysis (e.g., how did we fare? did we allocate funds correctly?).

Myth #2 – Project Management software is too expensive

If your idea of project management software involves purchasing servers, and purchasing a software application from a major vendor for a small practice with 10  practitioners  then, yes, it  is too expensive. If, however, you have gone cloud and elected to use a powerful web-based project management solution (such as Smartsheet), then you are likely to save thousands of pounds while reaping the benefits of a pay-as-you-go price structure. The present, and future, lie in cloud solutions that provide equal, or superior, functionality at a fraction of the cost.

Myth #3 – Project Management methodologies will slow us down

Project  managers  have  a reputation of using  process-intensive  methodologies  that favour ideology over pragmatism. In some instances this may, indeed, be the case when  there is a mismatch between a specific project management approach and the organisation’s acutall needs (e.g., a process-driven method, such as PRINCE2, may not be appropriate for a slightly chaotic environment that favours an adaptive approach, such as Scrum). So, in sum, put down the paint roller (“Project Management isn’t for us!”) and take out your fine-bristled brush (“The Critical-Chain method may not be our cup of tea, but Agile on the other hand”¦”).

Myth #4 – Facts and figures are more important than feelings and perceptions

While facts are very important, projects are often derailed and sabotaged because of false perceptions.  The PM must pay attention to both fact and fiction to navigate through turbulent  organisational change.

Myth #5 – Project managers need to be detail oriented and not strategic in nature

While it is of the utmost importance for the project manager to understand how to read the details of the project, they must also understand how the project supports organisational objectives.  Having a strategic perspective adds great value to the skill-set of the project manager.

Myth #6  Rely on the experts in everything that you do

It is true, we do need to rely on the experts but our trust can not be a blind faith.  The job of the project managers in this area is twofold.  First we must extract information and second we must verify that the information is accurate.  A good example of this is asking a planner  to provide an estimate on the effort required to perform a task.  In some instances team members forget to include tasks which ultimately results in a faulty estimate.

Myth #7  All the battles have to be fought and won so that we can succeed

Project managers sometimes make the assumption that they need to stand firm to get the job done, however, coming to compromise  on a particular issue is often a better course of action  in order to  win the war.

Myth #8 Project Managers  can wear multiple hats  

Wearing different hats can be extremely confusing.  This is especially true if the project manager is asked to be a business analyst or technical expert on top of serving in their PM role.  They end up doing  both roles with mediocrity.  When we “wear two hats” we essentially tell ourselves that both hats fit on one head at the same time. However, what happens if the demands of two roles conflict  and what assurances do we have that we’re managing the inherent conflict of multiple roles  and the  risks the  roles introduce? Sadly, multiple roles become more common as we move up the management hierarchy in an organisation, and that’s exactly where potential conflicts of interest can do the most harm.

Myth #9  Once the risk register is created, it’s full speed ahead

Risk management provides a forward-looking radar. We can use it to scan the uncertain future to reveal things that could affect us, giving us sufficient time to prepare in advance. We can develop contingency plans even for so-called uncontrollable risks, and be ready to deal with likely threats or significant opportunities.  Too often, it’s not until a catastrophic event occurs and significantly impacts project progress that ongoing risk reviews are conducted.

Myth #10 Project managers can not be effective in their role unless they have specific technical expertise in the given field that the project falls  within

You don’t need to be an engineer to manage a construction project or a IT  technician to manage a software development project.  All you need is a  fundamental  understanding with strong PM skills to manage  the team.  Experience in the field helps but does not guarantee success.

Project management is challenging enough without the myths. The profession has come a long way since the 1990s and some of these myths are fading. However, we still see remnants of them in one form or another.  Great projects cut through false assumptions and confusion, allowing their teams to make smart decisions based on reality.

These are just 10 project management myths, what are yours?  

Posted on

The Hard Side of Change Management

Change management is an approach to transition individuals, teams, and organisations to a desired future state. For over three decades, academics, managers, and consultants, realising that transforming organisations is difficult, have avoided  the subject.

My Way or the Highway

Major organisational change is profoundly difficult because the structure, culture, and routines of companies  often reflect’s persistent and difficult-to-remove ways of working, which are resistant to radical change even as the environment of  organisations change.

What started out as a financial buzzword in the early nineties  has become fundamental business practice, with executives recognising the need to keep abreast  with the competition in a rapidly developing corporate new world.

Navigating  change

Globalisation and the constant innovation of technology result in a constantly evolving business environment. There is an ever-increasing need for Change Management Lead’s / Senior Managers who can help organisations successfully navigate change in today’s business environments. The focus of this movement to date has been on how to  partner with organisations to define education, training and communication platforms that help to support the change initiatives and concerns of company employees. The critical aspect is a company’s ability to win the buy-in of their organisation’s employees on the change initiative.

While a project team is important for success, a senior level advisor is invaluable and can work  with an organisations  leadership team to avoid common pitfalls that change management projects often fall into. There are four key areas where an Advisor should act as this resource as follows:

1. Defining A  Strategy  

Executives should start by asking themselves  what exactly needs  changing and why? Organisational change directly affects all departments from entry level employees to senior management and  must be aligned to a  companies  strategy. Too many programs are heavy on the jargon and light on the substance.  Executives are often sold on an idea only to realise as the change initiative begins that they need a different outcome, tool or process to be successful.

In this situation the strategy for change needs to be re-aligned with the organisation and its goals.

An outside senior advisor with a unique perspective of the organisation will  play an important role in helping an executive to explore and shape the strategy they are defining and highlight whether it will truly create the outcomes they desire. This upfront partnership can save money  on the back end of a project, by avoiding costly re-scoping of initiatives.This relationship  between senior advisor and executive should therefore begin as early as possible in the process.

2. Coalition Building

Its important to give  people multiple opportunities to share concerns, ask questions, and offer ideas  and to make following up with answers and updates a top priority.  Executives must reach out across their functional work streams to build a large cohesive team to support the project once the correct strategy has been set and the urgency for the project has been established. A good senior advisor will be able to guide an executive though these interactions.

As a senior change management professional, it is important that you help leaders of the organisation craft the correct message. While leaders often know what it is they want and see the urgency for themselves, the outside view that a coach provides can support the development of a team around the initiative and  help to navigate the strategic and political interests in linking the change to the interest of multiple team members.

The more people are involved in the process, the fewer will  be acting as internal saboteurs.

Communication Is Key to Successful Change Management

3. Communication

Don’t confuse process visioning, planning and endless powerpoint presentations with communication.  

Change is uncomfortable, and adapting to change is messy. A  Gantt chart can not capture  the  hard side of  change management. Why? Because tasks are easy to list, but behaviour and long-held habits are not easy to change. Gather outside information, solicit perspectives, and adapt the approaches for your organisation and group.

The importance of communication within an organisation around the change cannot be underestimated.     Executives often fall short on communication in two main  areas, not communicating the right message and not communicating it frequently enough across an  organisation. It is often thought that everyone else in the organisation is on board and understands the change, however, the  reality for an executive  is not the reality for another worker who may have lost a job because of a well intended change initiative.  A senior advisor can apply consistent pressure to the leader of the change around the need for communication and its messaging.

Quantity Is Fine, but Quality and Consistency Are Crucial

4. Share  Relevant  Information Quickly

Most CEOs and managers are quoted as saying, “You can’t communicate too much,” Part of the communication will be the support the urgency in messaging.     “My way or the highway”  is often used, but is not an effective communication strategy.     Senior Advisors can work with executives to tailor their message to each area of the organisation in order to define content that is important to them.

A study by  Towers Watson  shows that “only two-thirds (68%) of senior managers say they are getting the message about the reasons behind major organisational decisions. Below the senior management level, the message dwindles further  to  (53%) of middle managers and 40% of first-line supervisors understanding  reasons behind major organisational  change.

The forwarding and cascading of information does not work as  consistent communication around the change will be necessary at all levels of the organisation using a variety of communication pathways and vehicles.  As a trusted advisor it is important to encourage executives to lead by example in both their messaging and communication of the change  agenda.

Only 25% of Change Management Initiatives Are Successful over the Long Term

Maintaining The Change

Many leaders and managers underestimate the length of time required by a change cycle. It is paramount  that as the  change effort reaches its completion that  leaders of the change recognise that the process does not end there.   The role of a Senior Advisor will be to guide them to the idea that work must be undertaken  to maintain the change over time. Maintaining change does not mean that an executive must own the initiative  forever, just that they take the necessary steps to ensure that change has a lasting impact by integrating the change into the corporate culture and measuring the benefits  and highlighting areas for future improvements.

The outside unbiased view is  that a Change Management Lead is crucial to the success of a change management program.

This article  provides food for thought rather than counsel specifically designed to meet the needs of your organisation or situation.  Please use it mindfully.

Posted on

4 Lies about Procurement You Probably Believe

The world of Procurement is seemingly full of impassioned people absolutely certain about what procurement is all about. Like other great lies, many of these half-truths and misleading ideas sound agreeable to the ears and come packaged as good advice from influential people.

How many of these popular lies have you fallen victim to?

1. Procurement should have a seat at the C-table

It’s not so much an outright lie as an irritating half-truth – but the damage comes with what Procurement people do with it. The thought behind this is well-intended: Procurement people should be able to speak the language of senior executives as easily as they can talk about FIDIC or demand forecasting. Terms such as EBITDA, ROIC, and economic profit should be part of their everyday parlance. Procurement issues are often the least understood by the board and the CEO and must be explained in their language.

What on earth could be wrong with that?   Nothing – if the Procurement people have full cognisance of their own tools and language – and can be persuasive to senior people of the value of Procurement.  

Now, that’s where we have, what is kindly referred to, as a skills gap.

In reality, for Procurement with no reputation (outside of that pesky metric of cost) and few business-aligned projects to call upon, it can be incredibly hard to try and catch senior people’s ear – never mind a C-seat (see what I did there?).

2. You must carry out a competitive tender to obtain value for money

I’m trying to distance myself from the public sector here (noting I did co-author the CIPS book on contracting in the public sector) but even in the private sector there’s a desperate need to get three quotes.  

Why three quotes?  

Not five, not 11?   ‘Cos the rules say three; that’s why.  

And the rules of Procurement policy and procedures, well, they can’t be broken because the CFO or the head of internal audit (all very commercial animals?) will be down on Procurement like a ton of bricks.  

When the three quotes are received the following conversation occurs – the highest price is rejected – ‘they’re ripping us off’ followed by – and I love this one about the lowest price quotation – ‘the price is too low, they must have got the specification wrong’ – and the contract is awarded to the middle-priced one”¦.surely there’s a better way to deliver value for money?  

Perhaps starting with actually defining it!

3. Procurement is the only source of governance for 3rd party spend

Being the only source would suggest a 100%, right?  

I’d be amazed – and delighted – if Procurement governed half of all the 3rd party spend.   Words such as ‘influencing’ are sometimes bandied about to shore up this lie. What a surprise that sales people are either trained, or very quickly learn ways, to actually bypass Procurement when selling.

And the reason?

Obviously marketing, IT, auditors fees, construction/property, recruitment (I could go on) is completely different, say the senior people in those departments – echoing the views of the oh so helpful sales people.   And Procurement just never gets near, as they can’t articulate (deliver?) the value they can add.  

I await the avalanche of people commenting on this telling me I’m wrong.   Please be assured you are exceptional in Procurement.    

4. Procurement welcome innovation and strategic relationships and anything other than lower price

Few businesses view Procurement as a strategic process. Most often, Procurement staff report to the CFO. This astonishing trend indicates that Procurement is still viewed as a financial / accounting activity and not an operational strategic activity that directly impacts the bottom line.

Suppliers; if you have an innovative product or service, recognise that Procurement’s ‘raison d’être’ is to deliver cost savings.   That’s what they are measured on, that’s what the research with CPOs and the C-suite say is the #1 priority.   There’s oodles of other priorities such as local sourcing, sustainability, innovation, partnering, risk management – I could go on and on and on.   But that’s the one they get measured on. Think that through, next time you’re pitching.    

The take-away

Perspectives on Procurement need to change, mature and grow up.  Lies like these need to be re-evaluated and abandoned. Procurement needs to change the way they engage and manage suppliers and their internal stakeholders; ‘adding value’ (a dreadful phrase!) means so much more than asking for a discount.

Stephen Ashcroft BEng MSc MCIPS (speaking here, very much in a personal capacity!) is Associate Director, Procurement and Commercial Advisory at AECOM, a Fortune 500 company. He’s a procurement learner stuck in the body of a procurement veteran, and with over 20 years’ experience still sees the glass as half full. Working with leading organisations across diverse industry sectors, Steve helps clients reimagine procurement to drive improved performance. A recognised advisor, speaker, lecturer, and author; the ever-hopeful Kopite shares his bright-eyed/world-weary views on Twitter @ThinkProcure, LinkedIn and his blog.

 

As seen on