| Course | DDBA 8511 Seminar in Innovation Management |
|---|---|
| Week | Week 4 |
| Paper type | Portfolio analysis |
| 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 4
Thirteen Percent Exploration and a Review Habit That Will Cut It: A Portfolio Analysis of a Commercial Lighting Maker's Fourteen Development Projects, Judged on Balance Rather Than Rank
Student Name
Walden University
DDBA 8511: Seminar in Innovation Management
Instructor Name
Month Day, Year
Thirteen Percent Exploration and a Review Habit That Will Cut It: A Portfolio Analysis of a Commercial Lighting Maker's Fourteen Development Projects, Judged on Balance Rather Than Rank
Why Not a Ranking
Bright Arc Lighting, a composite maker of LED fixtures for warehouses, schools and parking structures in Ohio, has 14 development projects funded for the coming year, with a combined budget of $6.8 million. The new chief executive asked for an analysis of the portfolio. The obvious response would be to rank the projects by expected return and cut the bottom few. A ranking would answer which projects are best. It would not answer whether the set as a whole leaves the company able to do anything new, which is the question March (1991) placed at the center of organizational learning: firms that put too much into refining what they already do improve in the short run and risk being left behind, while firms that put too much into searching for new possibilities never collect on any of them. This analysis classifies the projects on that dimension and judges the balance.
Classifying the Projects
I classified each project as exploitation, which refines existing products, processes or customers, or exploration, which pursues new technologies, products or markets the company does not serve. Classifications were made from each project's charter and checked with its lead.
Eleven projects refine what Bright Arc already sells: higher efficiency for its warehouse high-bays, a cheaper housing for school fixtures, a refreshed parking garage line. Three explore: grow lights for indoor farms, fixtures with sensors that report occupancy to building systems and ultraviolet fixtures for disinfecting air in schools and clinics.
Table 1
Projects by Type and Budget
| Type | Projects | Budget | Share of budget | |
|---|---|---|---|
| Exploitation: efficiency, cost and refresh of existing fixtures | 11 | $5.9 million | 87 percent | |
| Exploration: horticultural grow lights, networked sensor fixtures, ultraviolet disinfection | 3 | $0.9 million | 13 percent | |
Classification from project charters, confirmed with project leads; budgets from the fiscal 2027 plan.
Is the Balance Right?
No share is right in general. But Bright Arc's situation argues for more exploration than 13 percent. Its core market, LED retrofits of older warehouse and school lighting, is maturing: the company's own sales data show that about 60 percent of its customers' facilities have already converted. Prices for standard fixtures have fallen about 8 percent a year for three years. A company whose main market is shrinking and commoditizing needs a larger stake in what comes next. Tushman and O'Reilly (1996) argued that firms facing such shifts must manage incremental and discontinuous change at the same time, and that firms excellent at the first often fail at the second.
The Review Habit That Will Cut Exploration
Even the 13 percent may not survive. Bright Arc reviews every project quarterly against a single test: is it on track to its revenue forecast? Exploitation projects can meet that test, because their forecasts rest on known customers. Exploration projects cannot, because their early quarters produce prototypes, pilots and learning rather than revenue. The networked sensor project, for example, has no paying customer yet by design; it is running two pilots. In the first quarter in which exploratory projects look worse on the revenue test, which is every quarter for the next year, the review habit will push money toward the eleven that look better. Benner and Tushman (2003) found that process management practices designed to improve efficiency tend to shift attention and resources toward exploitation and away from exploration over time. Bright Arc's quarterly review is such a practice.
What Would Protect Exploration
Two changes would let the exploratory share survive. First, review exploratory projects against learning milestones, such as pilot results, customer interviews and cost per unit at small volume, rather than revenue. Second, protect the exploratory budget as a fixed pool for at least two years, so that one weak quarter does not move money to refresh projects. The chief executive might also consider raising the exploratory share toward 20 percent, funded by trimming the two exploitation projects with the smallest expected gains.
What the Chief Executive Asked and What This Answers
The chief executive asked for a portfolio analysis expecting a ranking. This analysis gives something different: a judgment that the portfolio leans too far toward refinement for a company whose core market is maturing, and a diagnosis of the habit that will make the lean worse. A ranking could still be produced within each category, and the two lowest-value refinement projects are identified in the recommendation, but cutting them only makes sense once the balance question is answered.
Limits
The classification involves judgment: the cheaper school housing could be seen as exploring a lower-cost segment. And the analysis does not assess whether the three exploratory projects are the right ones, only whether the portfolio leaves room for any.
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
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 4 instructions ask for
The fourth week asks you to analyze an organization's portfolio of development projects for balance between exploration and exploitation. Explain why a ranking would not answer the question. Classify each project, using its charter and a conversation with its lead, and report the shares of projects and budget in each category. Judge whether the balance suits the organization's situation, using evidence about its markets rather than a general rule. Then examine the organization's review practices and explain whether they will let the exploratory share survive periods when its results look weaker. Recommend changes to the review process or budget. Note where your classifications involved judgment. Cite research on exploration, exploitation and process management. Four to five pages with one table is typical.
How this DDBA 8511 Week 4 example is built
The analysis opens by explaining that a ranking would cut the projects that look worst in the short run, citing March's account of the pull toward refinement. A table classifies eleven refinement projects at 87 percent of budget and three exploratory projects at 13 percent. A section judges the balance against a maturing retrofit market and falling prices, drawing on Tushman and O'Reilly. The review habit section explains that quarterly revenue tests suit refinement projects and punish exploratory ones, such as the sensor project running pilots with no paying customer, citing Benner and Tushman. Recommendations include learning milestones for exploratory projects, a protected two-year pool and a possible rise toward 20 percent.
DDBA 8511 Week 4 rubric: what earns full marks
Credit goes first to refusing to rank and explaining why balance is the right question. Classifications should be made transparently and checked with project leads. Instructors weigh the judgment of balance most when it rests on evidence about the firm's markets, such as conversion rates and price trends. The analysis of review habits earns substantial credit, because it identifies the mechanism that would erode exploration regardless of intentions. Recommendations should address that mechanism directly. Acknowledging where classification involved judgment shows care. Sources should frame both the balance question and the effect of process management. One clear table of shares lets the reader check the balance claim. A clear proposal for protecting exploratory budgets earns further credit.
Common DDBA 8511 Week 4 mistakes, and how to avoid them
Portfolio papers often rank projects by return. Instead, sort each project by whether it refines what you already do or searches for something new, and total the budget in each group. Then ask what your markets suggest you need more of. Look closely at how projects are reviewed: what test do they face each quarter, and can an exploratory project pass it? If not, propose a different test for those projects and a protected budget. Admit where a project could fit either category. A tutor can help you classify your organization's projects. Report the budget share in each category, not just the count of projects.
Get a DDBA 8511 Week 4 example written to your instructions
Paste in the Week 4 portfolio prompt, the rubric, and the project list your instructor supplied, and a weighted portfolio analysis comes back in 24-48h with no charge the first time. Note the firm's review cadence if the case describes it. Weightings in the sample answer its own project set; the balance your list supports may be quite different.
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 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 8511 Week 11: Innovation Synthesis Paper
- DDBA 8521 Week 4: Incentive Conflict Analysis
- DDBA 8307B Week 4: T-Test Assumption Check
- DDBA 8303 Week 4: Interview Protocol
- DDBA 8300 Week 4: Research Question Audit
DDBA 8511 Week 4 questions, answered
Where can I find a free DDBA 8511 Week 4 sample paper?
Scroll down for the full portfolio analysis with its classification table; it is free.
How much of the DDBA 8511 Week 4 portfolio explores?
Three of fourteen projects and about 13 percent of the $6.8 million budget.
Why does the analysis argue for more exploration?
The firm's core retrofit market is maturing and fixture prices have fallen about 8 percent a year.
How will the review habit squeeze exploration?
Quarterly reviews test every project against a revenue forecast, which exploratory projects in pilot cannot meet.
What changes does the analysis recommend?
Learning milestones for exploratory projects, a protected two-year budget pool and a possible rise toward 20 percent.