MT400 Unit 7 Process Redesign Proposal Example

Reviewed by Chester Goodwin, MBA Business Process Management Purdue University Global Free custom sample in 24 to 48h

Remove first, move second and add tools last: this MT400 Unit 7 redesign proposal applies that order to five changes in a window installer's path from signed contract to cleared payment. Each change opens with the Unit 4 handoff finding it answers. The sales representative books the measure at the kitchen table, the manager's signature is dropped on standard orders, financing is approved before measuring, kits are checked before scheduling and the homeowner signs the completion certificate at the walkthrough. Projected gains of 4, 3, 1 and 9 days sum to 17, taking the median from 71 days to about 54, and each change names its own risk. A two-month pilot in Lincoln, with Omaha as comparison, tests the whole. Purdue Global MT 400 sets this proposal in the BS in Business Administration.

CourseMT400 Business Process Management
UnitUnit 7
Paper typeProcess redesign proposal
LengthAbout 880 words, 6 pages double-spaced
FormatAPA 7 student paper
SchoolPurdue University Global
ProgramBS in Business Administration
UpdatedOctober 2026

Free sample paper for MT400 Unit 7

1

Remove, Move, Then Tools: An MT400 Unit 7 Redesign Proposal for a Window Installer's Contract-to-Cash Process

[Student Name]

Purdue University Global

MT400: Business Process Management

Unit 7 Process Redesign Proposal

[Instructor Name]

[Date]

The company, changes and projections are composite; the notation and sources cited are real.

What this part is doingStating the order of moves in the lead tells the reader why no software appears in this proposal.
2

The Order of Options

Hammer (1990) urged companies not to automate a process before asking whether its steps should exist at all. The proposal follows that order strictly. Each change states which move it uses: remove, move or, last, add a tool. A current-state BPMN diagram and a future-state diagram face each other, with changed elements outlined, so the board can see exactly what is different.

Change One: Book the Measure Before Leaving the Home

Finding: at handoff 1, a signed contract sits for a median 9 days before anyone books the technical measure. Move: the sales representative books the technical measure on a shared calendar before leaving the homeowner's home, within five business days. Projected effect: the wait falls to about 5 days, a gain of 4. Risk: sales representatives may resist taking time at the kitchen table; the pilot tracks how many bookings are made on the spot.

Change Two: Drop the Sales Manager's Signature on Standard Orders

Finding: the approval loop at handoffs 3 and 4 adds 3 days and catches almost nothing on standard orders. Remove: the signature is dropped for standard orders and kept only for orders over $25,000 or with unusual shapes, about one order in ten. Projected effect: a median gain of 3 days. Risk: errors the signature occasionally caught on standard orders; the remake rate will show whether any appear.

Change Three: Approve Financing Before Measuring

Finding: financed orders sometimes wait at release for the financing company's approval. Move: financing approval is requested at signature, so it is complete before the measure, and the order can release the day its measure is verified. Projected effect: a median gain of about 1 day, larger on financed jobs.

Change Four: Check the Kit Before Scheduling

Finding: about one install in eleven begins with pieces missing from the kit, because crews are scheduled on partial receipt. Move: scheduling waits for a kit check two days before installation, confirming every unit, trim piece and fastener is on hand. Projected effect: little change in the median, but fewer return visits and a higher first-visit rate. The measure sheet's notes field is added to the order system at the same time, so site conditions reach order entry.

Change Five: Sign the Completion Certificate at the Walkthrough

Finding: completion slips wait a median of 11 days before invoicing, and 15 percent lack a signature. Move: the homeowner signs the completion certificate at the final walkthrough on a tablet, and the crew lead photographs it that afternoon so accounting can invoice the same day. Projected effect: installed to paid falls from 11 days to about 3, a gain of 9 in the contract-to-cash median, though still partly paced by how fast homeowners pay.

Seventeen days come out of the median because five named waits get shorter, not because of one hopeful estimate.

What this part is doingShowing the total as a sum of named causes makes the projection checkable against the pilot.
3

Projected Effects on the Indicators

The gains add up: 4 days from change one, 3 from change two, 1 from change three and 9 from change five, 17 days in all, bringing the contract-to-cash median from 71 days to about 54. Contract to installed is projected to fall from 58 days to about 50. First-visit success is projected to rise from 78 to about 85 percent and the remake rate to fall from 6.8 to about 5.0 percent, mainly from change four and the notes field. Status calls are projected to fall from 1.9 to about 1.2 per job, and the rating to rise from 4.1 to about 4.3. Redesign heuristics rarely improve time, cost and quality all at once (Reijers & Liman Mansar, 2005), and the projection shows where this redesign trades: change four may add a day for some jobs while removing return visits.

Who Does What Differently

The redesign changes the work of five roles. Sales representatives book measures and start financing at the kitchen table. The sales manager reviews only large or unusual orders. Order entry receives the measure sheet's notes and releases orders the day measures are verified. Schedulers wait for the kit check before confirming an install date. Crew leads collect the signed certificate and photograph it before leaving the site. Each role receives a one-page change sheet and a short training session before the pilot starts.

The Pilot

A two-month pilot runs at the Lincoln showroom, with the Omaha showroom as a comparison that keeps the current process. The same six indicators are measured in both. If the remake rate in Lincoln rises above its baseline for two consecutive weeks, change two is paused. The pilot is judged on contract-to-cash median, first-visit success and installed to paid, and results will be reported in Unit 10.

What the Proposal Does Not Include

No software is proposed here. Whether a workflow system adds value once these changes are in place is the question for the Unit 8 business case, which will measure the system against the redesigned process rather than the current one (Dumas et al., 2018).

What this part is doingEnding by deferring tools to a later case keeps the proposal faithful to its own order of options.
4

References

Dumas, M., La Rosa, M., Mendling, J., & Reijers, H. A. (2018). Fundamentals of business process management (2nd ed.). Springer. https://doi.org/10.1007/978-3-662-56509-4

Hammer, M. (1990). Reengineering work: Don't automate, obliterate. Harvard Business Review, 68(4), 104-112.

Reijers, H. A., & Liman Mansar, S. (2005). Best practices in business process redesign: An overview and qualitative evaluation of successful redesign heuristics. Omega, 33(4), 283-306. https://doi.org/10.1016/j.omega.2004.04.012

The Purdue Global MT400 Unit 7 instructions

In Unit 7 students propose a redesigned version of the process they analyzed. Instructors expect each change to answer a specific finding from the earlier analysis, not a general wish for speed. The course teaches an order of options: eliminate steps that add nothing, reorder or relocate steps whose timing causes waits, and consider automation only for what remains. Current and future states should be modeled side by side in the same notation, with changed elements marked. Each change needs a projected effect on the indicators from Unit 5 and a risk it carries. Many sections expect a short implementation plan, and a pilot with a comparison site is the most persuasive kind. Software is usually reserved for the next unit's business case unless the prompt says otherwise.

Inside the MT400 Unit 7 example

The example states the order of options first, citing Hammer's warning against automating a broken process. Five change sections follow, each built the same way: the finding with its days, the move used, the projected effect and the risk. Booking the measure on the spot answers a 9-day wait; dropping the signature removes a 3-day loop on orders under 25,000 dollars. A highlighted line says the 17 days come from five named waits, not one hopeful estimate. Effects on all six indicators come next, with Reijers and Liman Mansar on the tradeoffs redesign heuristics carry. A section lists what changes for five roles. The pilot plan names Lincoln, Omaha, the measures and a stop rule on remakes, and a last section defers software to Unit 8.

Reading the MT400 Unit 7 grading rubric

Redesign proposals are typically marked on how well each change answers the analysis, whether the course's order of options is respected, how credible the projections are and how practical the implementation looks. Rubrics in this course often reward elimination and reordering ahead of automation. Credit goes to projected effects shown as sums of named causes, since they can be checked against results. Naming a risk for every change, and how the pilot will detect it, shows judgment. Before and after models in matching notation make the changes visible. A pilot with a comparison site and a stop rule usually scores higher than a full rollout. Points also go to a clear account of who works differently, clean diagrams and APA 7 references for Hammer and the redesign heuristics.

MT400 Unit 7 help from the desk

A frequent weak proposal opens with a software purchase, which skips the step the course cares about most. Another lists improvements with no link to the earlier findings, so the reader cannot tell which wait each change shortens. Projections are often a single total with no breakdown, which no one can test. Risks are left out, or treated as resistance to change in general rather than a specific failure. Future-state diagrams sometimes use different notation from the current state, making comparison hard. Implementation is often one sentence. Before submitting, list each change beside the handoff it answers and the days you expect it to save, then add them up. If the total looks larger than the waiting you measured, one estimate is too hopeful.

Get an MT400 Unit 7 example written to your instructions

Handoff findings from earlier in your term, or the scenario in your Unit 7 prompt, become a first custom redesign proposal at no charge, with current and future states drawn in whatever notation your instructor requires. Turnaround is 24-48h. Sections that want automation weighed in this unit rather than later get that discussion included. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.

More MT400 papers and BS in Business Administration samples

MT400 Unit 7 questions, answered

Can an MT400 redesign proposal recommend software?

It can, once the steps themselves have been reconsidered. Most rubrics in this course expect elimination and reordering first, with automation argued only for what remains. If your prompt asks about technology, name the process change the tool would support and show that the change works on paper before any purchase is proposed.

How detailed should the future-state model be?

Detailed enough that every change is visible against the current state, and no more. Keep the same notation and level for both so a reader can compare them side by side. Outlining or shading changed elements helps. A future state far more detailed than the current one makes the comparison harder, not easier.

Do I need a pilot plan in the proposal?

Many sections expect some implementation plan, and a pilot is the most persuasive kind because it limits risk. Name where it runs, for how long, what it measures and what would stop it. A comparison site or period strengthens it further. If your prompt asks only for the design, a short paragraph on piloting still helps.

Where can I find a free MT400 Unit 7 sample paper?

You can read the complete MT400 Unit 7 redesign proposal here, with five changes to a window order flow and a pilot plan with a comparison showroom.

Why does the MT400 Unit 7 sample propose no software?

The course order removes and moves steps first, and the proposal leaves the question of whether a system adds value for the Unit 8 business case.