KOM_TSK7
BOLDFlash – Internal Business Process Artifacts
After several months on the job, Roger Cahill called a meeting with all department heads and stated:
Having had the chance to observe operations now for several months, it is obvious to me that we do not have sound business processes in place in a great many areas. We are creating problems for ourselves that are impacting product quality, delivery timeliness, efficiency, costs, and, my greatest concern, customer satisfaction.
Competition within our marketplace is heating up, and we need to quickly get on top of our processes to regain the confidence of our customers and make BOLDFlash their first choice when purchasing.
Cahill then presented examples of the internal business processes in use at BOLDFlash. To highlight the broad nature of the problem throughout the Mobile Division, he presented troublesome process examples from every department. (A subset of the examples follows.)
To reinforce the importance of establishing solid business processes, Cahill closed by saying:
Within the next 45 days, we will focus on establishing clear, efficient, defined business processes and gain agreement on these processes among all departments. This is now your top priority.
As you read the following process-related memos, consider how other department heads and their staff members might interpret the processes being introduced or revised and what their reaction might be. Also consider whether the communications are clear, unambiguous, and workable. Are there gaps or assumptions? Are there any common themes among the memos?
Memo #1 - Revised R&D Product Release Process
Memo #2 - Product delivery commitment process
Memo #3 - Product enhancements
For Internal Use Only
BOLD BOLDFlash Corporation 18 Commerce Boulevard
Manchester, New Hampshire
From: Karl Melzer - Director, Product Development To: All department heads Subject: Revised R&D product release process
R&D is making changes to the product release process so that we can reduce the time we’re spending on putting this together.
The new manufacturing package will no longer include special notes, because we already send these to Kevin’s admin assistant. We’re also dropping the product documentation because that’s sitting on a server so already out there.
The manufacturing package will now be made available 5 business days prior to production start. I know this puts a squeeze on Mfg., but we always need more time to work on it.
Finally, I’m directing my staff to no longer respond to questions coming on from Tech Support prior to actual product release date. We are continually crunched for time and need to move on to the next product release as quickly as possible.
Karl
For Internal Use Only
BOLDFlash Corporation 18 Commerce Boulevard BOLD Manchester, New Hampshire
From: Chip Bryant - Director, Sales To: All department heads Subject: Product delivery commitment process
We have been running into problems with customer orders where requested delivery dates are not being met—a very hot topic at a recent Sales staff meeting. So to eliminate the problem going forward, we are implementing the following process beginning immediately.
Sales reps will check in with Manufacturing on product availability against our requested ship date. If we don’t hear anything back within 2 business days, we will assume that the order can be filled and shipped per our requested date, and we’ll confirm back to the customer.
Chip
For Internal Use Only
BOLDFlash Corporation 18 Commerce Boulevard BOLD Manchester, New Hampshire
From: Kavita Patel - Director, Marketing To: All department heads Subject: Product enhancements
Representatives from Marketing have been attending a number of industry trade shows this season. We are receiving a lot of feedback that customers are looking for more enhancements to existing products. We are also seeing our competitors paying more attention to enhancements.
I have directed my staff to focus on identifying enhancements that we can make, particularly to our new flash drive line. We’re going to look at enhancements that can generate some “flash” in the marketplace for our product!
Time is of the essence with these new enhancements. We are confident we can keep these changes simple and not rock the boat too much. So that we can speed this along, the team will feed those requirements directly to Manufacturing.
This new approach will give us a great story for our upcoming trade show in Las Vegas, so I know everyone will be behind us in this!
Kavita
- BOLDFlash – Internal Business Process Artifacts
- For Internal Use Only
Accessibility Report
- Filename:
- IT 520 BOLDFlash Internal Business Process.pdf
- Report created by:
- Organization:
[Enter personal and organization information through the Preferences > Identity dialog.]
Summary
The checker found no problems in this document.
- Needs manual check: 2
- Passed manually: 0
- Failed manually: 0
- Skipped: 1
- Passed: 29
- Failed: 0
Detailed Report
Document |
||
| Rule Name | Status | Description |
|---|---|---|
| Accessibility permission flag | Passed | Accessibility permission flag must be set |
| Image-only PDF | Passed | Document is not image-only PDF |
| Tagged PDF | Passed | Document is tagged PDF |
| Logical Reading Order | Needs manual check | Document structure provides a logical reading order |
| Primary language | Passed | Text language is specified |
| Title | Passed | Document title is showing in title bar |
| Bookmarks | Passed | Bookmarks are present in large documents |
| Color contrast | Needs manual check | Document has appropriate color contrast |
Page Content |
||
| Rule Name | Status | Description |
| Tagged content | Passed | All page content is tagged |
| Tagged annotations | Passed | All annotations are tagged |
| Tab order | Passed | Tab order is consistent with structure order |
| Character encoding | Passed | Reliable character encoding is provided |
| Tagged multimedia | Passed | All multimedia objects are tagged |
| Screen flicker | Passed | Page will not cause screen flicker |
| Scripts | Passed | No inaccessible scripts |
| Timed responses | Passed | Page does not require timed responses |
| Navigation links | Passed | Navigation links are not repetitive |
Forms |
||
| Rule Name | Status | Description |
| Tagged form fields | Passed | All form fields are tagged |
| Field descriptions | Passed | All form fields have description |
Alternate Text |
||
| Rule Name | Status | Description |
| Figures alternate text | Passed | Figures require alternate text |
| Nested alternate text | Passed | Alternate text that will never be read |
| Associated with content | Passed | Alternate text must be associated with some content |
| Hides annotation | Passed | Alternate text should not hide annotation |
| Other elements alternate text | Passed | Other elements that require alternate text |
Tables |
||
| Rule Name | Status | Description |
| Rows | Passed | TR must be a child of Table, THead, TBody, or TFoot |
| TH and TD | Passed | TH and TD must be children of TR |
| Headers | Passed | Tables should have headers |
| Regularity | Passed | Tables must contain the same number of columns in each row and rows in each column |
| Summary | Skipped | Tables must have a summary |
Lists |
||
| Rule Name | Status | Description |
| List items | Passed | LI must be a child of L |
| Lbl and LBody | Passed | Lbl and LBody must be children of LI |
Headings |
||
| Rule Name | Status | Description |
| Appropriate nesting | Passed | Appropriate nesting |