BPM starts with grasping improvement of workflow (process model). Please benefit from the following process improvement activity story.
- Episode 1: How to draw a Business Process Diagram?
- Episode 2: What kinds of business can we kaizen (improve) remarkably?
- Episode 3: How to Exercise Knowledge Management under Application Control?
- Episode 4: How to Balance Productivity Improvement and Acquisition of Customers' Trust?
BPM-story-en.pdf (606KB)
Table of contents
- 1-1. I wonder what "Business Flow Diagrams" refers to ...
- 1-2. Go back or forward; "Decision"
- 1-3. Better leave it to a specialist.
- 1-4. Tons of Loops
- 1-5. After many twists and turns...
- 1-6. Want to refer to previous data
- 1-7. Application control by BPM software
- 1-8. In addition, after that...
- 2-1. Originality Rather Than Cooperativeness…
- 2-2. Points to Manage
- 2-3. Advice to a Proposal
- 2-4. Not All Proposals Require Advice
- 2-5. Cooperativeness Is Also Important
- 2-6. Proposal Basis? Or Project Basis?
- 2-7. Improve Reusability of Proposals
- 2-8. Grasp the Important Point
- 3-1. Meaning of Inquiries from Customers…
- 3-2. Also Inquiries within the Company
- 3-3. Formulated Recording of Responses
- 3-4. Start with Resolving Lack of Information
- 3-5. If No One Knows, Create Information
- 3-6. Drafts by Two People Is Better Than Ones by One Person
- 3-7. Discussion on Organization Policy Triggered by an Inquiry
- 3-8. Establishment of Consensus
- 4-1. System Integrator
- 4-2. Complaints of Entrusters
- 4-3. Contents of Tests
- 4-4. Explicit Specification and Implicit Specification
- 4-5. Specification Management
- 4-6. Revision Control
- 4-7. Besides Specification Determination and Acceptance Inspection
- 4-8. Timing to Brush Up a Process Itself
