0101 Using ProcessStep

ProcessStep Usage: Scenario 1

ProcessStep: a Project tool (where there is a definitive start and end period)

ProcessStep is used in a Project when there is:

  • The need to create Processes for a given set of Outcomes.

  • The need to clarify Roles and Responsibilities.

  • A business case for improving or changing current work Processes.  For example where companies are initiating organizational changes (combining or splitting up departments) and need current state/future state work. ProcessStep could yield Process improvement and provide a plan to implement the future state.

  • A requirement for Performance Management.

  • Business Risk that must be addressed through improved controls and checks.

  • The need to develop Workflow automation and ProcessStep will serve as a method with which to do the business analysis phase of the Workflow Automation Project.

  • The need to document business Processes:

    • For a Quality Management System.

    • As Operating Manuals.

    • As Training Material.

ProcessStep Usage: Scenario 2

ProcessStep: the tool for Change Management and Business Process Re-engineering (for ongoing Process work as part of Business Performance and Assurance Management, but planned and delivered as one or several Projects).

Change Management involves continued review of current Processes, establishing how activities could result in improved Outcomes and what people and systems are needed to make the changes.

By mapping out the current Processes, a base line is created from which to design improved practices. From this basis, a number of Workshops, will lead to improved or best practice Processes.   Implementation is driven by means of Action Lists.

Who uses ProcessStep?

ProcessStep has a varied application, not only in terms of the output that is needed, but also in terms of who would be interested in ProcessStep as a tool:

  • Browsers (including students, academics, business persons), who want to read the high and detail level “how to” of Process architecture, documentation, management and application in Performance, Change, Risk, Quality and Financial Management.

  • Process and other consultants, who want to use ProcessStep as a tool for earning their fees with and to enhance their consulting skills.

  • Instructors, who want to offer Process methodology as a training course, adding ProcessStep to their portfolio of training material.

  • Individuals wanting to learn about Process methodology in a virtual classroom environment.

  • Corporate Process practitioners.         

ProcessStep Approach

Processes form the basis of “what to do” to achieve Outcomes.  In order to achieve new, different and/or improved Outcomes, there has to be a vision on what those should be.  ProcessStep’s approach is to understand the vision and then define, create and document Processes using the ProcessStep Methodology in order to achieve the desired vision.  This is illustrated in the ProcessStep Approach Profile:

 ProcessStep starts by looking at what the current Process status is compared to vision. 

By addressing the  aspects of Processes, the Business aspect along with the People, IT and Compliance aspects of change are addressed in Process Workshops and Work-sessions and recorded in Process Maps and Action Lists.   Processes may be further detailed in Process Books, Management Element Definitions and Workbooks. (This information will be provided in future releases).

Once ProcessStep has established these aspects:   the further Phases of Testing, Implementation and Evaluation follow in pursuit of achieving the vision of the Entity.

ProcessStep views each assignment as a “Project”.  In terms of ProcessStep, “Project” is the activity with a specific start and end date that uses the ProcessStep methodology and toolset to bring about desired Outcomes.

[ Previous Page - 0101 Welcome]  [ Next Page - 0101 ProcessStep Structure]