DB FPX 8730 Assessment 2 Design Process Case Study example

Reviewed by Blythe Cavendish, PhD Managing Innovation, Design, and Creativity Capella University Free custom sample in 24 to 48h

This DB FPX 8730 Assessment 2 sample paper is a design process case study of an oil-management redesign for the fry station in commercial kitchens. It belongs to Capella DB FPX 8730, Managing Innovation, Design, and Creativity, which students in the Doctor of Business Administration (DBA) take as DB-FPX8730. The paper justifies the chosen design method against alternatives, reports each stage as an event with dates and participants, and keeps unproductive stages in the account rather than cutting them. It counts the outputs honestly, including ideas that went nowhere, and draws lessons for the firm's innovation process, including what the single stage gate would have done to this project.

CourseDB FPX 8730 Managing Innovation, Design, and Creativity
AssessmentAssessment 2
Paper typeDesign process case study
LengthAbout 1,100 words, 5 pages
FormatAPA 7 student paper
SchoolCapella University
ProgramDoctor of Business Administration (DBA)
UpdatedSeptember 2026

Free sample paper for DB FPX 8730 Assessment 2

1

Designing for the Fry Station: A Design Process Case Study of an Oil-Management Redesign, With the Method Justified Against Alternatives, Stages Reported as Events, Unproductive Stages Kept In, and Outputs Counted Honestly

Student Name

Capella University

DB FPX 8730: Managing Innovation, Design, and Creativity

Instructor Name

Month Day, Year

What this part is doingThe title names the design problem and the case study's discipline. Design process studies are judged on honesty about what did not work, so the unproductive stages are promised.
2

The Problem and the Method Justified Against Alternatives

Ironline Foodservice Equipment's largest quick-service customer reported that its restaurants were discarding fryer oil earlier than necessary in some stores and too late in others, raising oil costs and harming food quality. Crews were supposed to test oil daily with test strips and filter it on a schedule, but compliance was uneven. Ironline assembled a team of two engineers, an industrial designer, and a product manager to redesign the oil-management experience. Three methods were considered. A voice-of-customer survey of restaurant managers would have been quick, but managers were not the people doing the filtering, and survey answers would describe the official procedure rather than what crews did. A lead-user approach, working with the most advanced customers to find solutions they had already built, was attractive but the team could identify no restaurants that had solved the problem. Design thinking, which Brown (2008) describes as a human-centered approach that moves through observation, ideation, and rapid prototyping, was chosen because the problem appeared to lie in how crews actually worked at the fryer, which only observation would reveal. Liedtka (2015) argues that design thinking's value may lie partly in reducing decision-makers' cognitive biases, such as projecting their own preferences onto users; that was a specific risk for a team of engineers who had designed the existing filtration system.

What this part is doingThe method is chosen against named alternatives. Scorers reward case studies that justify the method before reporting it.
3

Stages Reported as Events

Observation, weeks 1 to 4. Team members spent 11 shifts in six restaurants, working beside crews during opening, lunch, and closing. They recorded 38 observations of filtering and oil testing. The key finding was that filtering took place at closing, when crews were tired and rushing, and that the filter pump's hose was stiff and hot, so many crew members skipped filtering or did it partially. Test strips were often stored in a manager's office and not used. Ideation, week 5. A two-day session with the team and two restaurant general managers produced 64 ideas, which were grouped and voted on. Five were selected for prototyping, including a sensor that measured oil quality continuously, a lighter hose, and a filtering reminder tied to the fryer's cook cycles rather than the clock. Prototyping and testing, weeks 6 to 14. The team built rough prototypes of the five ideas and tested them with crews in two restaurants. Two ideas worked: the continuous oil-quality sensor with a simple three-color light on the fryer, and an automatic filtering cycle triggered during a slow period in the afternoon. A redesigned hose helped but was not decisive. Crews said they liked it, but filtering rates with the new hose alone changed little, which suggested that the hose was an irritation rather than the main cause.

Unproductive Stages Kept In

Not every stage produced results, and the unproductive ones are part of the account. A two-week attempt to design a mobile app that reminded crews to filter produced a prototype that crews ignored; phones were not allowed on the kitchen line in most restaurants, a fact the team learned only after building it. A second round of ideation, held in week 10 to address closing-time fatigue, produced no ideas stronger than those already being tested. And one restaurant withdrew from testing after two weeks because its manager changed, losing data on the reminder concept. The app was built before anyone asked whether crews could use phones on the line.

Outputs Counted Honestly

The process produced 38 observation records, 64 ideas, five prototypes, and two concepts that moved forward into engineering. In the two test restaurants, over six weeks, oil was discarded based on the sensor rather than the calendar, and the operators estimated oil use fell about 15%, though that estimate rests on two stores for a short period and on the operators' own records. The automatic filtering cycle raised the share of days with a completed filter from about half, by crew report, to nearly all days, as recorded by the fryer's controller. Neither result has been tested at scale, and the six-week period included no holiday peak, when fryers run hardest, and the continuous sensor adds about 400 dollars to the fryer's cost, which the customer has not yet agreed to pay.

What the Process Cost

The process was not free, and its cost belongs in the account. The four team members spent about 60% of their time on the project for 14 weeks, roughly 1,340 hours in total. Restaurant visits required travel to three states, and the five prototypes cost about 38,000 dollars in parts and machining. Two restaurant general managers gave two days each to the ideation session, which the customer counted as a contribution. Against these costs, the team's view is that observation alone justified the effort, because it overturned the engineering team's assumption that crews skipped filtering out of carelessness rather than because the equipment made it hard.

What this part is doingOutputs are counted, including those that failed, and their evidence is qualified. Scorers reward honest accounting.
4

A Verdict About Fit, Not Virtue

Design thinking fit this problem well, and the reason is specific: the cause of poor oil management lay in the physical and social conditions at the fryer during closing, which neither a survey of managers nor the engineers' own knowledge would have revealed. The method's weaknesses also showed. It generated many ideas cheaply but did not screen out the phone app early, because the team moved to prototyping before checking basic constraints of the work setting, and its evidence of results is too thin to justify a cost increase without larger trials. The verdict is that the method fit a problem of hidden user behavior and should be followed by conventional engineering testing and a larger field trial before launch. If the team ran the process again, it would check the constraints of the work setting, such as rules about phones, heat, and space on the line, before any prototyping began, and it would ask the customer to commit more restaurants to testing at the outset so that one withdrawal would not leave the results so thin.

Conclusion

Ironline chose design thinking over a survey and a lead-user approach because the oil problem lay in how crews worked. Observation found the cause, prototyping produced two promising concepts, and several stages produced nothing useful. Counted honestly, the outputs are promising but unproven, and the method fit the problem without replacing the testing that must follow.

5

References

Brown, T. (2008). Design thinking. Harvard Business Review, 86(6), 84-92.

Liedtka, J. (2015). Perspective: Linking design thinking with innovation outcomes through cognitive bias reduction. Journal of Product Innovation Management, 32(6), 925-938. https://doi.org/10.1111/jpim.12163

DB FPX 8730 Assessment 2 instructions, in plain terms

Assessment 2 in DB FPX 8730 has you run or document a design process on a real problem and analyze it. You choose a method, such as design thinking or a structured innovation process, explain why it suits the problem better than alternatives, describe each stage as it happened, including research with users, ideation, prototyping and testing, report stages that produced little, count the outputs and evaluate what the process achieved. The problem can be small as long as the process is real. Research on design thinking, such as Brown and Liedtka, and its critiques support the case study.

How the DB-FPX8730 Assessment 2 example is put together

Problem, method choice, staged record, verdict on fit. The opening establishes the problem in terms that make a design method plausible: an unclear need, a solution space that has not been explored, users whose behavior is not fully understood. The second block justifies the method against alternatives, with the criteria for choosing stated. The third is the staged record, treating each phase as an event with participants, activities and outputs, reported factually. The fourth examines what the process produced overall against what a conventional approach would likely have produced, which is the comparison that makes the case study evaluative. The closing states where this method fits and where it did not. Headings track the prompt, and any statement about how well the method works rests on published research.

DB FPX 8730 Assessment 2 scoring guide: what Distinguished looks like

The scoring guide weighs the justification of method, the stage-by-stage account, the inclusion of unproductive stages, the honest count of outputs and the evaluation. Method reaches Distinguished when justified against at least one alternative for this problem. The account scores higher when each stage is reported as an event with dates, participants and what happened, such as observing fry cooks during a lunch rush. Unproductive stages earn credit when kept in and explained. Outputs are judged on whether they are counted honestly, including ideas discarded and prototypes that failed. The evaluation should connect the process to what the portfolio review found. Research critiques of the method should be considered. Distinguished case studies are candid about what design actually produced.

DB FPX 8730 Assessment 2 help from the desk

Design case studies often present a tidy sequence of stages copied from a model, which hides how messy the real process was. Another weakness is choosing a method without saying why it fits this problem. Stages that produced nothing are dropped, making the process look more effective than it was. Outputs are inflated or not counted. User research is described in general terms rather than as specific observations. The evaluation does not link back to the portfolio review. Keeping a dated log of the process as it happens, then writing the case from the log, keeps the study honest and prepares the creativity intervention in Assessment 3.

Get a DB FPX 8730 Assessment 2 example written to your instructions

Send the Assessment 2 instructions and your DB FPX 8730 scoring guide, together with the problem and method your section specified if it named either. We write a custom example against those criteria and return it in 24 to 48 hours. The first custom sample is free, and it reports what a design process produced rather than what it promises. The paper above is an original model document written by our desk, not a submitted student paper and not an official Capella University document.

More DB FPX 8730 papers and DBA samples

DB FPX 8730 Assessment 2 questions, answered

Do I have to actually run the design process?

Follow your instructions, which differ on this. Where a real application is required, a small problem run properly beats a large one run notionally. Where a documented case is permitted, choose one with enough procedural detail that you can report stages rather than summarize outcomes, since the staged record is what the criteria are reading.

How small can the problem be?

Smaller than most people attempt. A single service interaction, one internal form, the way a team hands work to another: any of these gives a design method something real to work on and can be completed within the assessment. Large strategic problems tend to produce a process described in the abstract.

What if the process produced nothing useful?

Report it, examine why, and you will likely write a stronger paper than a colleague whose process succeeded. Method research is full of conditions under which these approaches fail, and a case that identifies one of them empirically is a genuine contribution to the argument the assessment is asking you to make.

Where can I find a free DB FPX 8730 Assessment 2 sample paper?

This page presents the full fry station design case, with the method justified against alternatives, stages reported as events, unproductive stages kept in and outputs counted honestly.

What if the process produced nothing useful in DB FPX 8730 Assessment 2?

Report it and analyze why. An honest account of a process that failed can teach more than one that succeeded, and the scoring guide rewards candor.