| Course | DDBA 8511 Seminar in Innovation Management |
|---|---|
| Week | Week 11 |
| Paper type | Synthesis paper |
| Length | About 800 words, 5 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | Doctor of Business Administration (DBA) |
| Updated | October 2026 |
Free sample paper for DDBA 8511 Week 11
Stop Saying Yes to Every Custom Request: A Synthesis Arguing That a Hydraulic Component Maker's Capacity to Explore Is Limited by a Practice It Performs Superbly, and What Ending It Would Free
Student Name
Walden University
DDBA 8511: Seminar in Innovation Management
Instructor Name
Month Day, Year
Stop Saying Yes to Every Custom Request: A Synthesis Arguing That a Hydraulic Component Maker's Capacity to Explore Is Limited by a Practice It Performs Superbly, and What Ending It Would Free
The Thesis
Innovation capability is usually discussed as something to add: a new lab, a venture unit, a creativity program. This paper argues the opposite for Keystone Hydraulics, a composite maker of hydraulic cylinders and valves for agricultural and construction equipment makers in Iowa with about 520 employees. Keystone's capacity to explore new technologies is limited by a practice it performs exceptionally well, rapid custom engineering for its largest customers, and it should stop doing most of it. Removing that practice would free the people and attention that exploration needs.
The Practice and Why It Is Excellent
Keystone's reputation rests on saying yes. When a tractor or excavator maker needs a cylinder with a slightly different stroke, mounting or pressure rating, Keystone's application engineers design it within two weeks and deliver samples within six. The practice wins business: about 70 percent of revenue comes from customer-specific parts, and the two largest customers rate Keystone first among their hydraulic suppliers for responsiveness. Last year the engineering group completed 340 custom designs. By any operational measure, the practice is a strength.
How the Practice Crowds Out Exploration
The practice consumes Keystone's best engineers. Of 24 engineers, 19 spend most of their time on custom requests, which arrive unpredictably and carry customer deadlines. The company's one exploratory project, electro-hydraulic actuators that combine a cylinder with an electric motor and controls, the direction equipment makers are moving as machines electrify, has been staffed by two engineers part time for three years and has slipped repeatedly. Each time a large customer needs a custom cylinder, an actuator engineer is borrowed.
March (1991) argued that refining what a firm already does wins out because its payoffs come sooner and with less doubt, and that this tendency is self-reinforcing: success in exploitation makes further exploitation more attractive. Keystone's custom engineering is exploitation in March's sense, refining existing technology for existing customers, and its success has steadily pulled resources from exploration. Leonard-Barton (1992) showed how core capabilities become core rigidities when the skills, systems and values that support them make new kinds of work difficult. At Keystone, the values attached to custom engineering, responsiveness above all and never saying no to a key account, make protecting time for exploratory work feel like a betrayal of customers.
Benner and Tushman (2003) found that practices designed to improve efficiency and reliability tend to shift a firm's activity toward exploitation over time. Keystone's engineering workflow system, built to track custom requests to their deadlines, measures every engineer's hours against customer orders; exploratory work appears in it only as overhead.
Why Stopping, Not Adding
The usual response would be to add: hire more engineers for exploration or create a separate unit. Both have been tried in small ways. Two engineers hired for actuators in 2023 were reassigned to custom work within a year. A separate unit, as Tushman and O'Reilly (1996) recommend for firms managing both kinds of change, would help only if its people were protected from the custom queue, which at Keystone means changing the queue. Adding capability without removing the practice that consumes it would repeat what has already failed.
What Stopping Would Look Like
Stopping does not mean ending custom work. It means stopping the practice of saying yes to every request on the customer's timeline. Keystone could offer a catalog of configurable designs covering about 80 percent of past custom requests, with standard lead times, and accept fully custom designs only for its four largest customers and only with eight-week lead times. An analysis of last year's 340 custom designs shows that about 230 could have been met from a configurable catalog with modest changes. That would free roughly a third of engineering time.
What It Would Free
A third of engineering time is about eight engineers. Dedicated to electro-hydraulic actuators, that would turn a stalled two-person project into a team able to deliver prototypes to two equipment makers within eighteen months. It would also free management attention, since the weekly engineering meeting now spends most of its time triaging custom requests.
The Risks of Stopping
Customers may resent longer lead times and move some custom business to rivals. Revenue could dip. That cost is real. But the equipment makers Keystone serves are electrifying their machines, and a supplier that can only make better conventional cylinders faster will lose their business more slowly but more surely.
Conclusion
Keystone's best practice is its main constraint. The seminar's reading on exploration, rigidity and process management points to the same conclusion: capability to explore is limited not only by what a firm lacks but by what it does well and too much of.
References
Benner, M. J., & Tushman, M. L. (2003). Exploitation, exploration, and process management: The productivity dilemma revisited. Academy of Management Review, 28(2), 238-256. https://doi.org/10.5465/amr.2003.9416096
Leonard-Barton, D. (1992). Core capabilities and core rigidities: A paradox in managing new product development. Strategic Management Journal, 13(S1), 111-125. https://doi.org/10.1002/smj.4250131009
March, J. G. (1991). Exploration and exploitation in organizational learning. Organization Science, 2(1), 71-87. https://doi.org/10.1287/orsc.2.1.71
Tushman, M. L., & O'Reilly, C. A. (1996). Ambidextrous organizations: Managing evolutionary and revolutionary change. California Management Review, 38(4), 8-30. https://doi.org/10.2307/41165852
What the DDBA 8511 Week 11 instructions ask for
The final week asks you to synthesize the seminar's reading into one argument about an organization's innovation capability. Instead of proposing something to add, argue that a practice the organization performs well limits its ability to explore. Describe the practice and the evidence that it is a strength. Trace the mechanism by which it crowds out exploration, using research on exploration and exploitation, core rigidities and process management. Explain why adding capability without stopping the practice has failed or would fail. Describe what stopping would look like in practice, with figures, and what it would free. Address the risks of stopping. Close by stating the general lesson. The synthesis is longer than earlier papers, about eight to ten pages.
How the DDBA 8511 Week 11 example is put together
The paper states its counterintuitive thesis and describes Keystone's custom engineering: designs in two weeks, samples in six, 340 designs last year and top responsiveness ratings. A section traces how custom requests absorb 19 of 24 engineers and repeatedly borrow from the actuator project, citing March's account of self-reinforcing exploitation and Leonard-Barton's rigidities, including the value of never refusing a key account. Benner and Tushman explain how the engineering workflow system counts exploration as overhead. A section explains why two hires in 2023 were absorbed and why a separate unit would need a changed queue. Stopping is defined as a configurable catalog covering about 230 of 340 past requests, freeing about eight engineers. Risks and the lesson close the synthesis.
Reading the DDBA 8511 Week 11 rubric
The synthesis is graded on the strength and originality of its argument. A thesis that runs against the usual advice must be supported by clear evidence that the practice is a strength and that it consumes what exploration needs. Instructors weigh the mechanism most heavily: drawing on several readings to show how the practice crowds out exploration, through people, attention and measurement systems, demonstrates synthesis rather than summary. Explaining why adding capability has failed strengthens the case for stopping. A concrete, quantified description of what stopping means, and what it frees, shows practicality. Honest treatment of the risks earns credit. The closing lesson should follow from the case.
DDBA 8511 Week 11 help from the desk
Synthesis papers often list what each reading says. Instead, pick one claim and use the readings as evidence for steps in the argument. To find a practice worth stopping, look at what your organization is proud of and ask what it consumes: people, time, attention or budget. Gather figures. Check whether past attempts to add exploration were absorbed by that practice. Define stopping precisely and estimate what it frees. Be candid about what stopping would cost. For help shaping a long argument, our writers can sketch the synthesis structure with you before drafting. Keep each reading tied to a step in your argument.
Get a DDBA 8511 Week 11 example written to your instructions
Enclose the Week 11 synthesis prompt, the rubric, and the organization you have studied all term, and a synthesis paper follows within 24-48h, with nothing charged for a first one. List any readings your instructor has made mandatory. Whatever practice the sample names is its own; which practice your organization gives up is a judgment only you are placed to make.
More DDBA 8511 papers and DBA samples
- DDBA 8511 Week 1: Innovation Boundary Discussion
- DDBA 8511 Week 2: Idea Origin Case Analysis
- DDBA 8511 Week 3: Strategy Position Paper
- DDBA 8511 Week 4: Innovation Portfolio Analysis
- DDBA 8511 Week 5: Innovation Structure Memo
- DDBA 8511 Week 6: Innovation Culture Appraisal
- DDBA 8511 Week 7: Partnership Value Case
- DDBA 8511 Week 8: Innovation Metric Critique
- DDBA 8511 Week 9: Business Model Analysis
- DDBA 8511 Week 10: Implementation Handover Brief
- DDBA 8521 Week 11: Change Ordering Seminar Paper
- DDBA 8307B Week 11: Statistical Decision Brief
- DDBA 8303 Week 11: Case Synthesis Report
- DDBA 8300 Week 11: Design Defense Paper
DDBA 8511 Week 11 questions, answered
Where can I find a free DDBA 8511 Week 11 sample paper?
The full innovation synthesis paper is shown further down this page, with no fee to read it.
What does the DDBA 8511 Week 11 synthesis argue?
That a hydraulic component maker's excellent custom engineering limits its ability to explore and should largely stop.
How does custom engineering crowd out exploration?
It occupies 19 of 24 engineers and repeatedly borrows people from the electro-hydraulic actuator project.
Why not simply add more engineers?
Two engineers hired for actuators in 2023 were reassigned to custom work within a year.
What would stopping look like?
A configurable catalog covering about 230 of 340 past requests, with fully custom work limited to four customers.