This page holds a finished NR 720 Week 2 process map write-up example: a swimlane map of one pathway as it actually runs, plus prose explaining what the crossings reveal. Searches like "nr 720 week 2 assignment example", "nr720 week 2 sample" and "nr 720 week 2 example" land here.
What a finished NR 720 Week 2 process map write-up looks like
Two artifacts arrive together and neither works alone. The map is drawn in swimlanes, one lane per department, so every arrow leaving a lane shows up as a crossing you can point at. Most maps here carry few enough steps that the whole thing reads on one page. The write-up is the argument. It walks the crossings rather than the steps, because a step inside a lane has an owner and a crossing may have none. Where the map shows a requisition leaving one lane, the prose says who releases it, who accepts it, what occupies the interval between those two acts, and whether either department's record covers that interval at all. Scope sits at the top: where the pathway starts, where it ends, what was left out on purpose.
How a NR 720 Week 2 example is structured
The write-up usually opens with scope and method, giving the start and end points, how the map was built and who confirmed it. The map follows, with numbered steps so the prose can point at things. The body then takes the crossings in the order the work meets them, and for each one records what leaves, what arrives, how the receiving department learns it has arrived, and how far apart the two versions of that moment sit. Next comes a short list of the steps that exist nowhere in policy, kept separate because they are frequently the map's most useful finding. The closing section states which crossing the writer suspects is carrying the failure and what about it remains unverified, which sets up the observation work that follows.
Why lanes decide everything
One lane per department makes each transfer between departments something you can point at. The single-line version buries the same information inside arrows that all look identical.
Built from people
A map assembled from a written procedure describes an intention. A map assembled by asking three people who perform the step describes a process, and that difference shows up every later week.
The steps nobody wrote down
Every real pathway carries invented steps: a call placed to check, a private list, a form completed twice. Listing them separately is often the strongest part of the submission.
What the interval hides
Between one department releasing something and the next accepting it there is time nobody is recording. Marking those intervals on the drawing is what turns it into a diagnosis.
Declare the edges
A write-up that states its start point, its end point and its exclusions can be checked. One that leaves all three implicit invites the reader to assume the worst about each.
Where marks go in NR 720 Week 2
Losing the actual process is the costliest error, and it happens whenever a writer builds the map from a procedure document rather than from the people doing the work. Almost as damaging is the flat map, one long line of boxes with the department changes buried inside the arrows, since the course's whole subject vanishes the moment lanes come out. There is also the write-up that narrates, restating in sentences what a reader can already see in the drawing, which spends the word count and adds nothing. Verification gets skipped often: a map nobody in the process has read back to you is still a hypothesis. Finally, maps that halt at the department line rather than following the work into the next lane stop exactly where this course begins.
Get a NR 720 Week 2 example written to your instructions
Send your Week 2 instructions, the rubric, and any mapping template or software the classroom requires, and a custom write-up with a matching swimlane map comes back inside 24-48h, first one free. If you have already sketched a map, send that as well and the sample can be built around your own pathway instead of a generic one, which makes the later weeks considerably easier.
NR 720 Week 2 questions, answered
Which mapping method should I use?
Sections differ, and a swimlane layout suits this course better than most alternatives because departments are the unit of analysis. Where the classroom names a method, use it and put lanes inside it. Dedicated software is not required either. A clean drawing made in a document, or drawn by hand and photographed, is widely accepted provided every step and every crossing is legible at reading size.
How much of the pathway should the map cover?
Enough to contain the crossing you care about and little enough to read without scrolling. Writers who map an entire service end up with something impressive and unarguable, while the ones who map from the request being placed to the result being acted on can say something specific. When in doubt, trim the ends rather than the middle, since the middle is where the departments meet.
Do I need permission from my employer to map a process?
For a course map of how work moves, generally no, though asking is worth the two minutes if you plan to quote anything internal. What you should not do is reproduce employer forms, screenshots or reports inside the paper. Describe them instead. The map belongs to your analysis, the source documents stay where they are, and nothing in the assignment needs them attached.