Your SlideShare is downloading. ×
Meet Justin & Peter
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Meet Justin & Peter

211
views

Published on

A simple story that is told in a powerful way …

A simple story that is told in a powerful way

Applied innovation - simply done


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
211
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Meet Justin & Peter
  • 2.
    • But first let me introduce Mike Oxley
  • 3.
    • and Paul Sarbanes
  • 4.
    • who together wrote a
  • 5.
    • after
  • 6.
    • &
  • 7.
    • which passed into
  • 8.
    • and created a ton of for Justin
  • 9.
    • A.K.A.
  • 10.
    • Mr. Junior Business Analyst
  • 11.
    • who works
  • 12.
    • and has to use
  • 13.
    • to document
  • 14.
    • which for a BA is like using a
  • 15.
    • But his boss
  • 16.
    • at the
  • 17.
    • sends him off
  • 18.
    • to talk to
  • 19.
    • and then their support teams
  • 20.
    • which makes him feel like
  • 21.
    • after studying
  • 22.
    • 5 different Visio diagrams
  • 23.
    • going to 10
  • 24.
    • reading 20 pages of
  • 25.
    • making 30 calls on the
  • 26.
    • and sending 50 chase emails
  • 27.
    • and doing lots of
  • 28.
    • the process model looks like
  • 29.
    • Now meet Peter
  • 30.
    • A.K.A.
  • 31.
    • Mr. Junior Business Analyst
  • 32.
    • who works
  • 33.
    • and also works for a
  • 34.
    • which has to document
  • 35.
    • for
  • 36.
    • so Peter just sends
  • 37.
    • to……….
    • Philip Jon James
  • 38.
    • and their teams
  • 39.
    • so they can do all the
  • 40.
    • and just send him back the
  • 41.
    • which he can then flex his intellectual
  • 42.
    • by opening
  • 43.
    • He can see everyone’s processes
  • 44.
    • and view what each one wrote
  • 45.
    • and how they do things
  • 46.
    • He can review each one’s documentation
  • 47.
    • to agree with a company standard
  • 48.
    • simply understood by all
  • 49.
    • that is saved and published in the company
  • 50.
    • enabling Peter
    • to
    • update all
    • about
    • any changes
  • 51.
    • via RSS
  • 52.
    • and as
    • gives the code so
  • 53.
    • … ..he can use them in…..
    • … .his BPA tools……
  • 54.
    • …… to analyse and simulate…..
  • 55.
    • …… .then save it back in the library…..
  • 56.
    • … .which updates all the …
  • 57. … and then he engages with Kim
  • 58. … .and her Team
  • 59.
    • …… who manage
  • 60.
    • … .who use the
    • … in the
  • 61.
    • to automate parts of it
    • giving Peter time to …….
  • 62.  
  • 63.
    • with
  • 64.  
  • 65.
    • while poor
  • 66.
    • puts in more
  • 67.
    • until his boss buys him
  • 68. So Remember
    • turns text into diagram into code
  • 69. So Remember
    • is intuitive and can be used by
  • 70. So Remember
    • making brilliant for
    • Business Process Discovery
    • Documentation & Automation
  • 71.
    • www.ProcessMaster.com