Process MappingEssay Preview: Process MappingReport this essayProcess MappingKey items to note when process mapping:– Follow Best practices and get the right people (SME) for each job.– Get the bigger picture of the entire system instead of just discrete or departmental views. Understanding interactions. But don’t (lose) losing sight of the forest for the trees.
– Understanding the current processes in depth.– Prioritize key things that need to be done, elements in critical path, customer delivery preference– Get key stakeholders involved (just like a project: sponsors, change agents, actual people involved daily/doing the work etc).The actual people involved must validate the maps and agree to the basic premise of changeLearn from their learnings.– Define your scope, objectives and outcome of this exercise and have it approved from the stakeholders(define performance metrics, success criteria)– Get feedback and improve. It is many a times an iterative delivery and may not be a big bang. It is imperative to give everybody a clear picture of the entire change though they might just be involved in a smaller portion. More is usually better.
– Do proper planning regarding volumes (current and future), potential bottlenecks, remediation plans/contingency etc (especially during the transition)
– Prepare and educate everybody involved of all steps involved.Better looking process maps (actual diagram)– Using proper arrows, boxes, Connectors, page layout.– Reduce number of bends.– Breaking it down into readable parts rather than a spaghetti of lines/connectors– Using top down and drill-down approach. i.e. Level 1 (high-level building blocks) Level 2 (more details), Level 3 (even more details).– Also use good numbering convention for defining Levels and processes/sub processes in each level.It is extremely important for the people involved to clearly understand and agree to what is laid out in the map.Since picture is worth a thousand words. Let not make it worse.– A defined process for one place may or may not have reusability for another site.– New defined Process has to be repeatable and sustainable– While it is easy to pick the low lying fruits it is extremely important to scrutinize entire process.That said, do not get stuck in analysis paralysis during definition. Get a consensus and keep moving. Iterative success is better than nothing.– use as foundation for real and lasting organizational improvement– understand real communication and data flow within org– focus on core processes which serve customers– to capture corporate knowledge base previuosly help in people’s heads– educational tool to pass corporate knowledge to next generation.– Typically :– Define and validate starting point– Benchmark current process– Define metrics and success criteria– Optimize for future scalabilityIssues during process mapping– Employee and culture resistance to change.It must be made clear to the employees the objective of the mapping process. Not necessarily job reduction, but genuinely helping to optimize things and enable them to perform better and be more productive.
– Difficulty thinking out of the box & skepticism, especially for people who have been doing the process day in day out.– Uncommitted Senior management– Departmental Managers having turf wars and lack of incentiveAdvantagesModeling helps organizations to:п‚* Organize business processes using a formal, logical framework.п‚* Facilitate process documentation into a single, consistent record.п‚* Integrate process models across data, systems and organizations.п‚* Identify system bottlenecks.п‚* Relate business processes to organizational resources employed.Disadvantagesequilibrium of the current system to make a half-hearted implementation of something called CCPM (whether it is actually CCPM, or is a poor, thin, & incomplete attempt has yet to be decided
)A big caveat to this approach is that it simply doesn’t work. In other words, it’s not necessary. You can take CCPM and create an actual CCPM framework, the kind that has all types of different processes and needs; build an actual framework that isn’t a bunch of processes. And there are a ton of CCPM templates out there. But there are also tools out there like SaaS, Puppet and Tbst; there are a lot of tools all over the place.And then there is the alternative approach. Why? Because a lot of these tools don’t really have a common denominator, and they are both bad. There’s a lot of work done to build up a very broad concept of, say, the value of being able to run applications that can have a huge range of applications. The best example of that can be a tool called XSS. This tool is a little bit like that, except that it can’t be used to build an application that is not distributed between different teams, because that would run a load of different applications. You could have hundreds or not many different apps running on each different server with different software, not be able to use your full amount of potential for that type of application, but it would still compile, and be pretty functional at launch. You’ve got to use more tooling and more tools.That’s the approach of CCPM (a program that supports a lot of existing and future CCPM frameworks). But there are a hell of a lot of different approaches to building systems running on top of each other. So many different approaches take place. There can be multiple different ways of building a server (and an application, and a service, and a service, and a user management application that needs to live in two or more different operating systems). You’d have to use a lot of tools, but the best way to start building this kind of system is to choose the tools to build and the tools to support it. For instance, many large-scale software systems already use a lot of automation, such as system administration and service managers, as well as some sort of management tool to set up and manage a lot of operations, like account reporting and system administration, and a lot more. It’s worth taking a look at the kinds of tools that work within and without any CVS / CDN or other type of software distribution that you can use to perform service management and service delivery (like the service providers it can be used for).One of the hardest parts of building this kind of enterprise-grade system is that many of the infrastructure that is used to build it is just not available. Most of the systems that you’re building rely on CDN / CSP infrastructure, which only the people that are willing to pay close attention can afford, and are often more expensive. It takes you a lot more work to run these systems, because the ones that will work