• Products
    • Demos
    • TaskMap Standard
    • TaskMap Pro
    • Capture for Excel
    • TaskMap Central
    • Upgrade
  • Downloads
    • Trials
    • Templates
    • Free Role List
  • Training
    • Self-paced Tutorials
    • Online Seminars
    • Calendar
  • Solutions
    • ITIL Suite
    • SOX Expert Suite
    • SPM Roadmap
    • Consulting
    • Process Conversion
    • Process Templates
  • BPM Blog
    • Process Mapping
    • Process Discovery
    • Process Analysis
    • Improvement
    • Change Management
    • Articles
  • Support
    • Product Support
    • TaskMap
    • FAQ's
    • Contact
    • Self-Paced Tutorials
  • About
    • Contact
    • Partners & Resellers
    • Background

  • About the BPM Blog
  • BPM Blog Sitemap

BPM Blog

BPM made simpler

« How to evaluate operating effectiveness of your company (Part 2 of 2)
The problems with setting goals »

Upside down Procedures and Processes

Jul 27th, 2011 by TaskMap

 
Are we looking at it all wrong?

Do you ever get the feeling that you are seeing something very different than the other guy? I don’t just mean the glass half full/empty outlook on life, but fundamentally are we looking at things the wrong way?

I sometimes get that feeling when dealing with projects that involve processes, and all my projects are about processes! Take the following scenario, the stakeholder or client has a problem; they know they need to improve some processes in the organization, but are not sure exactly where to begin.

As the designated Agent of Change we provide them with guidance to determine goals and objectives to scope out the next steps. For example:

  • Need to document existing processes accurately
  • Train existing staff how to follow these processes
  • Be able to standardize the process for quality and efficiency

Before I continue, let’s go back in time …

Back to the Future

In 1770, James Watt pioneered the use of drawn-to-scale engineering plans for the manufacture andproduction process installation of industrial products[1]. These were used to assist in the successful deployment of his products; steam engines for factories driving the industrial revolution. Over time these plans evolved from crude drawings to assist an experienced engineer to more detailed plans that were created by a junior draftsman. This was the forerunner of today’s Computer Aided Design[2] world. Detailed, precise instructions permitted products to be manufactured without the need for hugely skilled labor, and a bridge was created between design and production engineering.

In many ways the Subject Matter Expert/Project Manager takes the same role today as those early engineers. Understanding in detail what needs to be done, and translating these complex processes by way of underlying skills, experience and well established methodologies.

The time may be right to go back and look at a different way of doing things; one that may change industry again.

Looking at the pie instead of the ingredients?

When an expert looks at a problem they often want to show off their skills. Look at me I am smart, indispensible, letters after my name, better than you … got the idea. Now all project managers are not this way, but there is a tendency to want to show off our skills versus others in the project.

One way this happens is we often/always start looking at process FIRST. Because we are good at seeing the big picture, grasping the complex, overanalyzing the simple; so we habitually start with the complete process.

As a result we are often way ahead of where the client/stakeholder is in the project. Being ahead a few steps is probably OK; being so far ahead they can’t see your dust creates distance, misunderstanding and communication problems. They may not feel that you are on the same wavelength, and we all know where that leads. We don’t want to go there.

Start with the tasks, not the process.

Recently, I have been examining this problem with some precision. I know Business Process Management has the word process in the middle, and is therefore important. However, every process is full of tasks, activities and decisions. The client/stakeholder may not yet see how all these tasks are intertwined to make up their own work processes, but they understand the basis of all processes are tasks. So why don’t we start by capturing the tasks first? Good idea!

A task centric approach has several advantages over process first. These include:

1. It’s easier to get the client/stakeholder to capture precise information about roles, ownership, guidelines, resources, timeframes, frequency etc. on a task basis

2. Once you have all the important tasks documented it’s easier to then order them for the “as is” or “current state” of operations

3. Get everyone on the same page for the process documentation project

4. Builds a base of foundation data for the project

Once this task library has been created, we can return to the process view. However now we have the details we need to build on our “Discovery” phase of the project. If you have used Excel or a similar product to capture this information, it will be easily sorted and can be then categorized for the process capture stage of the project.

Conclusions

Just as we learn the alphabet, words, sentences, grammar before creating great prose; we need to apply the same principles to our Process Management activities. Taking logical steps to breakdown the “Discovery” process into tasks and then build the jigsaw puzzle that is the process makes sense.

Given the potential for re-use of tasks in best practice models, this approach may have much merit in Process Improvement methods.

Copyright 2011 Michael J. Cunningham


[1] NMSI. The Production Process. May 20, 2011. http://www.ingenious.org.uk/Read/Seeing/Drawings/Theproductionprocess/.

[2] Wikipedia. Computer-aided Design. May 20, 2011. http://en.wikipedia.org/wiki/Computer-aided_design.

Tags: back to the future, deployment, drawings, efficiency, factories, goals and objectives, guidance, james watt, org uk, scope, stakeholder, steam engines, wrong way

Posted in Change Management, Process Mapping

Leave a Reply

Click here to cancel reply.

  • Archives

    • March 2012 (1)
    • February 2012 (3)
    • January 2012 (4)
    • December 2011 (11)
    • November 2011 (16)
    • October 2011 (17)
    • September 2011 (20)
    • August 2011 (21)
    • July 2011 (21)
    • June 2011 (22)
    • May 2011 (22)
    • April 2011 (23)
    • March 2011 (26)
    • February 2011 (28)
    • January 2011 (31)
    • December 2010 (31)
    • November 2010 (20)
  • Recent Posts

    • Business Process Modeling
    • Education
    • The issue of organizational culture
    • A VERY SHORT HISTORY OF PROCESSES
    • Process Dashboards: Identifying and flagging risk levels
    • Process Dashboards: Analyzing timeframes
    • THE CASE FOR PROCESS DASHBOARDS
    • Is 2012 the year that version control finally takes hold?
    • How to listen carefully to your team–Reflective listening skills overview (Part 8)
    • How to listen carefully to your team–Reflective listening skills overview (Part 7)
    • How to listen carefully to your team–Reflective listening skills overview (Part 6)
    • How to listen carefully to your team–Reflective listening skills overview (Part 5)
    • How to listen carefully to your team–Reflective listening skills overview (Part 4)
    • How to listen carefully to your team–Reflective listening skills overview (Part 3)
    • How to listen carefully to your team–Reflective listening skills overview (Part 2)
    • How to listen carefully to your team–Reflective listening (Part 1)
    • TaskMap Update: version 4.0.5
    • BPM BLOG Summary for week ending 2 December 2011
    • The Tutorials are coming … the tutorials are coming
    • The psychology of spending and how it can help BPM ;-)
    • Happy Thanksgiving
    • BPM Blog–The need to refine
    • Processes as instruction tools
    • BPM Blog Weekly summary 11.18.2011 with video blog
    • Project and Processes (responses to the questions)
    • Projects and processes
    • Thinking things through
    • Happy 11.11.11 and BPM Blog summary
    • TaskMap Automated tutorial: TaskMap Capture for Excel
    • Customizing fields in TaskMap 4 Professional
    • Prioritization in your life
    • The need to refine
    • Happy Anniversary BPM Blog: A good first milestone
    • Training the trainers
    • Power
    • BPM Blog summary for week ending 28 October 2011
    • Customized process mapping
    • Agile methodology: The case for a blended Agile
    • Additional displays: Are they worth the money?
    • BPM Blog summary week ending 21 October 2011
    • Thoughts matter: How thoughts affect our actions in everyday life
    • BPM Summary of automated tutorials on the TaskMap menu
    • Automated tutorial—Save as process folder
    • Automated tutorial—Task Links and how to use them
    • Automated tutorial for Task Details
    • TaskMap Tutorial—Save as PowerPoint
    • Check my TaskMap
    • BPM Blog summary week ending 7 October 2011
    • Renumbering Tasks in TaskMap
    • Customizing roles names in TaskMap
    • Adding tasks to a Page–add task to page Dialog
    • How to add tasks to pages using the auto connect feature in TaskMap
    • BPM Blog Summary Week ending 30 September 2011
    • Towards Perfection
    • BPM in the Legal Profession
    • BPM BLOG SITE MAP
    • Rigor and our business processes
    • BPM Summary Week ending 23 September 2011. The Case for a Blended Agile
    • The Case for a Blended Agile: Part 4-Agile Stepping Stones Approach
    • The Case for a Blended Agile: Part 3-What a blended approach looks like
  • RSS Get the BPM RSS feed

  • Posts by category

    • Change Management
    • Compliance
    • Law Processes
    • Legal processes
    • Org Charts in Visio
    • Process Analysis
    • Process Discovery
    • Process Improvement
    • Process Mapping
    • Project Management
    • Uncategorized
  • Tags

    best practices bpm budget business analyst business process category change change management computing group dashboard decisions discovery discovery phase efficiency flowchart flowcharts goals and objectives governance harvard job management change management project map methodology mike cunningham milestones personality process documentation process improvement process mapping process maps project management project managers quality standards return on investment risk role names sox compliance target task library team members technorati time and money timeframe Visio willingness

Home • Products • Downloads • Templates • BPM Blog • Training • Contact Us • SiteMap

Copyright © Harvard Computing Group, Inc., 1994-2011. All Rights Reserved. TaskMap is a registered TradeMark of Harvard Computing Group.
Harvard Computing Group, 225 Cedar Hill Street, Suite 200, Marlborough, MA, 01752, USA Tel: 978-800-4590