Make Business Process Realignment a Part of Every Technology Project

Do you ever wonder if your organization gets work done in spite of the rules, systems and processes that they have to follow?  I have been out working with clients for the last month and have heard and seen many people talking about this subject.  Based on a conversation that I had with a colleague and Performance Consultant, Dr. Karen McGraw, I wanted to share some thoughts on process realignment.

Business processes are an important part of the way work gets done. On many of our projects we are called on to implement not only the technology, but also to re-align business processes. Now these are the smart clients. They understand that implementing a new technology changes the way that people get their jobs done.

In many cases, new technologies subsume or change old processes. For example, at my last company, when we implemented InfoPath forms and automated processes in SharePoint, we create workflows based on the most effective ways to complete the process. SharePoint now orchestrates what previously was a manual process. The reviewers and approvers may be the same. But the way they receive the document or request, how they respond to it, and how it moves to the next reviewer changes.

In other cases the new technology we implement presents the opportunity to revise related business processes.  Some clients choose to use the new technology and simply keep the old work process. These clients often reason that even some change (the technology) is enough – they fell like buying a new set of clothes will help the person get the job done better.  However, this reasoning often results in a misalignment between what the technology can do for them and how they currently work.  By failing to realign business processes to include and build on the functionality provided by their (new or even existing) technology, they get less value from their technology than they could.

During the recession and post-recession recovery, we find ourselves being asked to help our clients “do more with less”.  To find ways to accomplish this you use a methodology like the Performance DNA methodology to conduct tool optimization projects and identify ways to better align new or existing technologies with the organization’s business processes.  I am always surprised to find that organizations spend considerable money on technology (Hardware and Software), but that the technology implementations have rarely examined the impact on business processes or even the training needed to take advantage of a better process.

How much more value could a tool provide the organization if processes were better aligned to take full advantage of what the tool could do? How much more productive would organizations be if all technology projects included realignment of business processes and training on how to apply the process using the tool?

So do you try to include process realignment on your projects?  How are your processes and tools working in your organization?

What is PMBOK All About?

Do you know what PMBOK stands for?  Project Management Body of Knowledge—WOW, that much knowledge could send someone running for the door. However, the book that PMI sells is called “A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Fourth Edition”.  The operative word in the title is really the lead-in, “A Guide to …” that concept is what I think is important about the PMBoK. This book was not written on stone tablets nor is it a set of rigid rules that should be executed without deviation. It is a set of project management standards, suggestions and best practices based on the vast experience of many professionals in the field.

On and off over the next few months, I plan on walking through sections of the PMBOK on the blog and offering the advice and observations of some of my very knowledgeable colleagues on key subjects. The latest edition of the PMBOK is available from PMI for $65.95 and to PMI members and students for $49.50. (This link can change with new versions and is also available at Published in 2013, the fifth edition is over 500 pages (yes it is a big knowledge area!) and covers all aspects of project management. A digital PDF and ebook is also available.

The first chapter of the PMBOK introduces the terms, definitions, and core responsibilities of a project manager.  Terms and vocabulary are an important part of the PMBOK (Not to mention Project Management) because it is how we communicate with language that describes meaningful concepts.  For example:

“A project is a temporary endeavor to create a unique product, service, or result”


“Project management is the application of knowledge, skills, tools, and technique to project activities to meet the project requirements.”

Project managers are responsible for “initiating, planning, executing, monitoring, controlling, closing” a project. Whew! Take a deep breath; you already knew project management was a big job.

One example of a concept and definition that has now been documented in the PMBOK for some organizations is the Project Management Office (PMO). The PMO may have responsibility for acting as a surrogate for stakeholders and decision makers. It is expected to help in managing shared resources across projects, identifying, training, and coaching best practices, and monitoring compliance with standards. PMOs may also produce general project policies, procedures, and facilitate sharing knowledge across the organization.

I believe PMOs to be invaluable in large organizations with multiple projects and complex projects that last over several years. In the past, I wrote two blogs about my experience and recommendations on PMOs including Getting a PMO Right is Worth the Effort and Do you need a PMO?

An interesting take on PMOs was offered by Cornelius Fichtner on his PM Podcast , “7 Trends in PMO”,  summarized by Team Frame. He points out that today PMOs have different reporting structures based on the organization’s needs. For example:

  • Large companies tend to have a central entity
  • Medium-sized companies may also have a central PMO, but the PMs report to the line managers rather than the PMO
  • Small companies seem to focus more on Communities of Practice (you may check out “How to Grow Communities of Practice” if you want more information )

Future PMO trends according to Fichtner include companies requiring PMO experience and certification, hiring consultant PMO experts and services, and greater availability of project management tools and templates—many of which will be free or very low cost.

As with all predictions about the future, I guess we will see how many of these seven predictions come true for future PMOs. Next week, I hope to bring an interview with a senior strategist exploring his views on current PMO activities, challenges, and future trends.

So the first part of the PMBOK is targeted at concepts, language and understanding of the field.  If you are trying to understand a new area (accounting, law, sales, programming, etc) it is always important to first learn the terminology and understand the concepts of that area.

The PMBOK is not the only book that purports to document the body of knowledge called project management – but it is probably the most widely utilized.

I will be exploring other areas of the PMBOK in future posts – are there any areas that you would like to hear about?

The Lazy Project Manager's Blog

The Home of Productive Laziness Thoughts

Thoughts, experience, tips and tricks on issues affecting managers and project management

A Girl's Guide to Project Management

Project Management musings for one and all

LeadingAnswers: Leadership and Agile Project Management Blog

Thoughts, experience, tips and tricks on issues affecting managers and project management

Project Management Hut

Thoughts, experience, tips and tricks on issues affecting managers and project management

Herding Cats

Thoughts, experience, tips and tricks on issues affecting managers and project management


Pushing the Edges Out ...


Just another site