jon pyke keynote address

1 May 22-24, 2007

Washington Dulles HiltonThe Business Transformation Conference

Jon PykeChairman Workflow Management CoalitionFounder and CEO The Process Factory

SessionTitle:Understanding your Organization’s Processes

WelcomeWelcome

to Transformation and Innovation 2007 The Business Transformation Conference

2 May 22-24, 2007


A DefinitionBusiness Process Management (BPM) is a natural and holistic management approach to operating business that produces a highly efficient, agile, innovative, and adaptive organization that far exceeds that achievable through traditional management approaches.

3 May 22-24, 2007


What’s it really all about?

Wikipedia defines Business Process Management thus:

“The term Business Process Management (or BPM) is a set of activities which organizations can perform to either optimize their business processes or adapt them to new organizational needs. As these activities are usually aided by software tools, the term BPM is synonymously used to refer to the software tools themselves.”

4 May 22-24, 2007


Data

SOA

Transactions

Think

Business Process Management Layer

Main Business Process

Compliance

Risk

Service Levels

Regulations

5 May 22-24, 2007


Why we do BPM*

Makes it easier to improve business processes and create new ones

Enables the automation of processes across the entire organization and beyond

Provides managers with real-time information on performance

Allows organizations to take full advantage of new computing services.

Puts existing and new processes under the direct control of business managers – no technology

* Source: Understanding your organization’s Processes – Pyke et al - CUP

6 May 22-24, 2007


Business Process ManagementIt’s about People

It’s about Business

It’s about managing performance

It’s about improved control

It’s not about SOA!!!

It’s not about Web Services Yucky technical stuff

The business need

7 May 22-24, 2007


BPM Evolution

• where these two technologies overlap• where they are different • which mathematical models to use• which standards are applicable to which part of the stack• and all that associated puff.

8 May 22-24, 2007


Origin discussions are behind us:

One technology begat the other– But now they appear to be diverging– Some platform vendors suggest BPM:

• It’s only about system-to-system

• People not involved

But we know different!!!

9 May 22-24, 2007


It sucksWorkflow sucks because poor assumptions

Too inflexible

People don’t tend to work that way

The unexpected is ever present

Not any of my products you understand

10 May 22-24, 2007


It sucksBPM sucks because it ignores carbon

But it’s good because of heritage

Systems do as you expect

BPEL4PEOPLE won’t fix the problem

11 May 22-24, 2007


It sucks

The Web sucks because it bombards us with too much info – most of which we can’t absorb

Web 2.0 will suck harder – because we’ll get even more stuff than we do now

12 May 22-24, 2007


Emerging Trends*

RFID VoIP IM retentionSMS retentionWorkgroup collaboration Tracking the content and distribution of:

– RSS feeds, – corporate blogs – internal wikis

*AiiM Emtag November 2006

13 May 22-24, 2007


Business will get harderMore complianceMore competitionMore control

But more informationMore unstructured communicationHarder to manage and track

14 May 22-24, 2007


EMAILFAX

PHONEFACE-TO-FACE

REPORTSBLOGSWIKIS

SOCIAL NETSINSTANT MESSAGING

WEB SEARCHMAILING LISTS

CHATVIDEO-CONF.

INTRANETERP

Workflow/ BPM

DocumentMgt.

Other Enterprise

Apps.

PLM

Source Peter Fingar

15

What’s the answer?

Understanding the business processes exist at 2 levels (the Silicon and the Carbon) takes us a long way towards understanding how we solve this potential problem.

16 May 22-24, 2007


The ComplianceGap

The Business Process – where two worlds collide

17 May 22-24, 2007


BPM as a Web Services mind setThe process is seen as a set of service interactions by the IT people – this is OK but doesn’t mean anything to the business

Logistics (Mainframes)

Customers(Databases)

Content/Personalisation

(Interaction Packages)

Customer Service(Client/Server)

Integration(EAI Packages)

ERP(Packages)

Java (Application Servers)

J2EEJ2EE

18 May 22-24, 2007


Portals

ERPPackaged Apps

Home-grown

Content Mgmt

Mainframes

Data

Windows

Terminal Apps

Unix

Supply Chain Partners Mobile WorkforceCustomers

Interaction

Integration

BusinessProcess

TechnologyProcess

19 May 22-24, 2007


Knowledge Intensive BPM

Process based technology that understands the needs of people and supports the inherent “spontaneity” of the human mind is the next logical step, and we might be tempted to name this potential paradigm shift “Knowledge Intensive Business Processes”.

All we know and love about BPM still valid– SOA, Web Services, Systems to Systems etc.

– IC-BPMS

But Human side is not simply forms routing and work queues

You’re managing cases!!!!

20 May 22-24, 2007


Knowledge Intensive BPM

The key differentiating factor of a case handling environment is the ability to run multiple procedures against a given case of work—the primacy is with the case rather than the process that is used to support a work item

Case Handling systems leverage the capability to associate virtually any number of objects within the context of a case– Processes, documents, attributes, resources, assets

Processes tend to “unfold” rather than rely on a priori design time decisions (but within the context of an overall framework)

21 May 22-24, 2007


ERP

Workflow/ BPM

DocumentMgt.

Other Enterprise

Apps.

PLM

HumanInteraction

ManagementSystem

Case A

Case C

Project B

Source Peter Fingar

22 May 22-24, 2007


Vertical Apps.

Doc. Mgt.

Workflow/BPM

ERPPLM

Business RulesKnowledge Mgt. Database

IT SYSTEMS

ProjectA

CaseB

Joe

Jim

Jane

Jill

JackJohnJen

Mgt. ControlCompliance

23 May 22-24, 2007


Key points to recognizeThe unpredictable actions of the carbon components are not ad-hoc

processes,

Nor are they exception handling (ask anyone with a six sigma background about exceptions and you’ll understand very quickly what I mean).

This is all about the unstructured interactions between people – in particular knowledge workers.

These unstructured and unpredictable interactions can, and do, take place all the time – and it’s only going to get worse!

The advent of Web 2.0, social computing, SaaS etc. etc., are already having, and will continue to have, a profound effect on the way we manage and do business.

24 May 22-24, 2007


Thank YouThank YJon PykeChairman Workflow Management CoalitionFounder and CEO The Process Factory

Contact Information:[email protected]

ou www.theprocessfactory.com

www.wfmc.org

jon pyke keynote address

Business

knowledge

jon pyke

process factory

software tools

web services

process

processes

business