Behn's purposes narrowed to three, evaluating, learning and budgeting, give a fare-capping trial its measures in this pilot performance measures example from MMPA 6451, Week 9. Searches like "mmpa 6451 week 9 assignment example", "mmpa6451 week 9 sample" and "mmpa 6451 week 9 example" land here.
What a finished MMPA 6451 Week 9 pilot performance measures looks like
The plan fills four pages. Up front sits the pilot's scope, two routes for six months, and the decision it will inform, whether to extend capping systemwide. Behn's eight purposes appear in a short table, with the three chosen purposes marked and the reason others were set aside. Each chosen purpose then gets a section with two or three measures defined operationally. Evaluating: change in trips per account among riders who reach the cap, against comparison routes. Learning: disputed-tap calls and lost-card transfers, which show where the process breaks. Budgeting: net fare revenue per route, computed as in the Week 7 formula. Every measure lists its data source, its owner and when it is reported. A last section names two measures deliberately excluded, overall ridership and rider satisfaction, and explains why each would mislead.
How a MMPA 6451 Week 9 example is structured
Scope and decision come first because a measure means nothing until its reader and use are known. Behn's framework sets the sequence: purpose before measure, since his central claim is that no single measure serves every purpose. The table of eight lets a reader see the choice being made, and reasons for exclusion matter as much as reasons for inclusion. The three sections follow the pilot's own logic, did it work, where did it strain, what did it cost. Comparison routes appear in the evaluation section because without them any change in trips could reflect season or service changes. Owners and reporting dates are attached to every measure so the plan reads as operational rather than aspirational. The exclusion section closes the plan by naming measures others would expect and explaining their flaws, which answers the obvious objection.
One pilot, one decision
Two routes, six months, and a choice about systemwide extension.
Eight purposes, three chosen
Behn's list in a table, with reasons for every purpose set aside.
Measures for evaluating
Trips per account among riders reaching the cap, compared with similar routes.
Measures for learning and budgeting
Disputed taps and card transfers show where the process strains; net fare revenue shows its cost.
Two measures left out
Overall ridership and satisfaction scores are excluded, each for a stated reason.
Where marks go in MMPA 6451 Week 9
Measurement plans score on fit between purpose and measure. A plan listing ridership, revenue and satisfaction as key performance indicators, without saying which decision each informs, has produced a dashboard rather than a plan, and graders in public administration courses tend to say so. Credit follows Behn applied as a selection device, with reasons for purposes excluded. Operational definitions are read closely: trips per account needs a period and a comparison, or it measures nothing. Comparison routes tend to lift a plan, since a pilot without them cannot separate its effect from season. Owners and reporting dates are commonly expected and often missing. The exclusion section earns credit by anticipating what a board member would ask for. Measures the agency cannot collect from its own systems weaken the plan quietly.
Get a MMPA 6451 Week 9 example written to your instructions
Describe the pilot or program your measures should serve and send its Week 9 prompt and rubric. The MMPA 6451 measurement plan comes back with purposes chosen, measures defined and owners named, in 24 to 48 hours, a first request free. The pilot routes and their city are invented, and no agency's actual data is used.
MMPA 6451 Week 9 questions, answered
What are Behn's purposes of performance measurement?
Robert Behn argued that public managers measure performance for eight purposes: to evaluate, control, budget, motivate, promote, celebrate, learn and improve. His point was that each purpose needs different measures, so a single set rarely serves them all. The example chooses three purposes for a pilot and defines measures for each. Your plan can use the list the same way, as a selection device rather than a checklist.
Why exclude overall ridership?
Because ridership on pilot routes can change for reasons unrelated to fare capping, such as season or service changes, and a systemwide figure would dilute the effect. The example measures trips per account among riders who reach the cap, against comparison routes, which isolates the riders the policy targets. Your plan can include ridership for context if you state that it cannot show the pilot's effect.
Does every measure need an owner?
Yes, in practice. A measure without an office responsible for collecting and reporting it tends not to be reported. The example assigns each measure to an owner, such as the fare systems group or customer service, with a reporting date. If your prompt does not ask for owners, adding them still strengthens your plan, because it shows the measures are collectible.