The hand-in for week 2 is one legible map of a single operation, drawn with consistent symbols, next to a walkthrough naming every handoff, every wait, and the step that limits throughput. Searches like "wmba 6040 week 2 assignment example", "wmba6040 week 2 sample" and "wmba 6040 week 2 example" land here.
What a finished WMBA 6040 Week 2 end-to-end process map looks like
One page carries the map, usually a swimlane with a horizontal band per role and boxes reading verb plus object: receive request, verify coverage, key the order. Diamonds mark decisions, and every arrow that leaves the diagram to come back later is drawn as the rework loop it actually is. Queues appear as their own symbol with a time written beside them, four hours here, two days there, because unmarked waiting is the thing a map exists to expose. A legend sits in the corner. Around the drawing, six hundred to eight hundred words follow the same path in prose, naming who owns each step and where the count of items entering stops matching the count leaving.
How a WMBA 6040 Week 2 example is structured
A short purpose paragraph opens, stating which operation is drawn and where the boundary sits, since the same order desk can be mapped in three defensible ways. The map follows as a numbered figure with a caption. Prose then walks it start to finish, one paragraph per phase rather than one per box, so the reader gets a sequence instead of a list. A small table usually accompanies the walkthrough: step, owner, typical time, observed volume, and the source behind each figure. Nothing appears in the walkthrough that the figure does not show, and no box on the figure goes unmentioned in the prose. Observations come after that, drawn only from what the drawing shows, and a final section names the step where flow is held back and shows which rows of the table support that reading.
Scope and boundary
Two or three sentences fixing where the operation begins and ends, plus the reason for that cut. Mapping from customer request to invoice paid and mapping from request to shipment produce different constraints, so the document owns the choice it made.
The figure itself
One page, one symbol set, roles in lanes, decisions as diamonds, rework arrows honest about how far back the work travels. Legibility is graded: a diagram that needs magnification or a verbal explanation has failed the purpose it was drawn for.
The walkthrough
Prose following the drawing in order, naming owners and describing what physically happens at each stage. It stays synchronized with the figure, which sounds obvious and is still the most common mismatch in submitted mapping documents.
Times, volumes, and their sources
A table pinning numbers to steps: how long work takes, how long it waits, how many items pass through in a week. Each row says where the figure came from, whether a stopwatch, a system report, or a marked approximation.
What the drawing exposes
A closing reading of the map: where items pile up, which approvals duplicate one another, which loop sends work backward. The limiting step is named here and supported by the table rather than by intuition.
Where marks go in WMBA 6040 Week 2
Mapping rubrics pay first for accuracy and completeness, meaning every handoff shown and no invented steps, and second for the reading that follows the drawing. The reliable deduction is a map with no time on it: a technically correct diagram that cannot support any claim about where an operation runs slow. Another is drift between figure and prose, where the narrative describes an approval the drawing never had. Symbol discipline matters less than instructors get credit for, but consistency does, and mixing three notations on one page draws comment. Where strong submissions separate themselves is the closing paragraph, which uses the drawing as evidence instead of restating it box by box.
Get a WMBA 6040 Week 2 example written to your instructions
Upload the mapping assignment with its rubric and the desk builds a sample map and walkthrough, returned in 24-48 hours, the first at no charge. If your section requires a particular tool, Visio, Lucidchart, or shapes in Word, or a fixed notation, say which one and the figure is produced that way.
WMBA 6040 Week 2 questions, answered
Does the map have to be drawn in specialist software?
Rarely. Most sections accept any legible figure, and shapes in Word or Google Drawings pass routinely, though Visio and Lucidchart output looks cleaner in a submitted PDF. What gets graded is whether roles, decisions, and waits are all visible and whether the notation stays consistent, not which program produced the file.
Should the map show the process as it is or as it should be?
Week two is almost always current state. The improved version belongs later in the course, once measurement has justified a change. If your prompt asks for both, label them clearly and keep the current state complete, because the comparison later loses its meaning when the starting picture was already cleaned up.
How much detail is too much for one page?
When a reader cannot follow the flow without a magnifier, the level is too fine. Group micro-steps that share an owner and a purpose into one box, and put the granular breakdown in an appendix if your rubric wants it. Fifteen to twenty-five boxes suits most operations at the scale this course assigns.