Not Every Project Is Growth
Why More Projects Can Squeeze a Company Instead of Making It More Profitable
Revenue is rising. The project count is climbing. The team has never been busier. Yet cash is not getting easier, delivery dates are slipping, and leaders wake up to a new fire every morning.
In a company like this, the problem is not too few projects. The problem is that the portfolio is growing faster than the organization can carry it. Every new project consumes cash, people, expertise, decision time, and risk capacity along with the revenue it promises.
Growing the number of projects is a sales achievement. Managing the portfolio so it remains profitable, on time, and cash-generating is management.
A Project Can Succeed While the Company Gets Weaker
Project management focuses on completing a defined piece of work within its scope, schedule, cost, and quality targets. Portfolio management focuses on the combined impact of all projects on the company.
A single project can look profitable on its own. But if it pulls critical engineers away from other work, consumes cash, or delays a more valuable delivery, it can weaken the company's overall result.
That is why a project's value is more than the difference between contract price and direct cost. Financing, warranty exposure, collection terms, management attention, and opportunity cost are also part of the real project economics.
Project profit appears in accounting; project burden shows up in cash much earlier.
Saying Yes to Every Project Is Not Growth
Before a project is accepted, management should ask: Does it fit the strategy? Is the contribution margin sufficient? Can the cash gap be financed? Do we have the required expertise? Are the contract terms balanced? Is the customer's payment behavior reliable? Is the scope clear? And which existing project or resource will this new work displace?
Most companies do not ask the last question. A new project is evaluated as if it were independent of the current workload. In reality, every project entering the portfolio triggers an invisible reprioritization.
Saying no to a project may cost a sale. Saying yes to work you cannot carry can cost the company.
An Open Slot on the Calendar Is Not Capacity
In project-based companies, capacity is not limited to production lines or headcount. Specialists, support functions, and senior management attention are shared across multiple projects.
A free day on the calendar does not mean a resource is truly available. If the same person is carrying three critical customer decisions, two technical approvals, and a field issue, that person has no real capacity.
Running resources at 100 percent utilization is not always efficiency; often, it means leaving no buffer for delay. A minor customer hold, supply problem, or technical revision can create a chain reaction across the entire portfolio.
Most Projects Break at the Point of Sale, Not in the Field
Ambiguous scope, unrealistic delivery dates, verbal side commitments, and weak payment terms can damage a project's economics before execution even begins.
When working with international retail groups such as Kingfisher, the size of the opportunity was never enough on its own. Product standards, quality, delivery discipline, supply continuity, and logistics capacity had to operate as one system. Large customers demand a correspondingly high level of execution discipline.
The sales-to-operations handoff is not a file transfer. It is a decision point where scope, delivery dates, payment terms, technical requirements, and change control are validated.
Systems, Not Project Count, Carry Growth
In a project-based company where I served as General Manager, monthly revenue grew from TRY 20 million to TRY 140 million, the workforce expanded from 17 to 87, and the active project portfolio increased from 7 to 33.
The real challenge was not winning more work. Finance, operations, sales, and project management had to become stronger at the same pace. Growth could not remain sustainable without systems that made projects visible and accountability explicit.
The central lesson was clear: as the number of projects grows, the decision system, cash visibility, authority boundaries, and management cadence must grow with it.
Now, Let's Pull a Rabbit Out of the Hat
DENGE: Five Questions Before You Accept a Project
I call this framework DENGE - the Turkish word for balance. It evaluates a project through five management questions:
VALUE
What does this project contribute to the strategy, the customer portfolio, and future growth?
ECONOMICS
What is the true contribution margin after risk and hidden costs are included?
CASH
Do the spending schedule and the advance, milestone billing, invoicing, and collection timeline align?
CAPABILITY
Do we truly have the people, expertise, operational capacity, and management attention to carry the project?
RISK
Are the contract, scope, customer, technical, and delivery risks acceptable?
A project should not be accepted simply because it is strong on one or two DENGE dimensions. High revenue potential cannot compensate for weak cash, a prestigious customer cannot compensate for inadequate capacity, and an attractive margin cannot compensate for ambiguous scope.
Senior Management's Job Is to Make Decisions, Not Listen to Reports
Project managers manage individual projects. Senior management manages the total impact those projects have on the company.
Senior leaders do not need hundreds of indicators. Contribution margin, 13-week net cash requirements, milestone performance, critical resource load, scope changes, cost-to-complete variance, overdue receivables, and the number of projects that remain commercially or financially open form a strong core dashboard.
Weekly meetings should focus on delays, resource conflicts, and near-term risks. Monthly meetings should produce decisions on new project acceptance, resource allocation, repricing, renegotiation, holds, or closure. Quarterly reviews should challenge the portfolio's strategic contribution and customer concentration.
The output of the meeting should be a decision, not a report.
A Project Is Not Finished When the Physical Work Is Done
Delivery may be complete. But if collection is still open, punch-list work continues, guarantees have not been released, warranty obligations remain, or unused inventory is still on the books, the project is still consuming the company's cash and attention.
An unfinished project occupies more than the schedule. It consumes organizational memory and decision capacity. That is why closing discipline is as important as winning new work.
What Should Happen in the First 90 Days?
In the first 30 days, map every active project's contract, scope, schedule, cash, and resources.
In the next 30, establish acceptance criteria and shared KPIs.
In the final 30, reprioritize the portfolio and make the first hold, renegotiate, or close decisions.
Conclusion: Growth Is the Portfolio You Can Carry
More projects do not automatically mean more growth. Growth means choosing the right work, allocating resources deliberately, protecting cash, and having the discipline to say no when necessary.
DENGE turns that judgment from individual instinct into a shared management language. High revenue potential cannot compensate for weak cash, a prestigious customer cannot compensate for inadequate capacity, and an attractive margin cannot compensate for ambiguous scope.
Senior management's responsibility is not to crowd the portfolio. It is to align the portfolio with the organization's carrying capacity. Real success is not measured by how many projects are launched, but by how many are completed profitably, on time, with positive cash generation, and without exhausting the organization.
Not every project is growth. Growth is the discipline of choosing the right work your organization can actually carry.
• • •
Editorial and Legal Notice
Nature of this article: This article is based on Orkun Akçasarı's professional experience, personal management approach, and original editorial analysis. It is not legal, financial, investment, audit, or independent consulting advice. Implementation decisions should be evaluated against each company's own data, contracts, risk appetite, and advice from qualified professionals.
Confidentiality and anonymization: Company, project, and workplace examples have been anonymized, generalized, or summarized without changing their substantive context where necessary to protect trade secrets, personal data, contractual confidentiality obligations, and legitimate third-party interests. Quantitative career results are drawn from the author's professional archive.
Third-party names and trademarks: Kingfisher is referenced solely and descriptively to explain the author's prior professional experience. This reference does not imply that Kingfisher plc, any affiliated brand, or any other entity endorses, approves, or currently maintains a commercial relationship with the author or this article. All rights in the referenced names and marks remain with their respective owners.
Ownership of views: All opinions, interpretations, and conclusions in this article are the author's own. They do not represent the institutional views of any past or present company, customer, shareholder, executive, manager, or employee with whom the author has been associated.
Intellectual property and the DENGE framework: The DENGE framework as presented in this article - including its five-part classification, explanatory language, examples, editorial sequence, and visual presentation - is original work by Orkun Akçasarı. The Turkish original and this authorized English-language adaptation, including their expression, structure, and presentation, are protected under Law No. 5846 on Intellectual and Artistic Works and applicable international rules. Any trademark or other industrial-property rights in the standalone name 'DENGE' depend on applicable registration and use conditions.
Use and reproduction: Subject to quotation, criticism, and other exceptions permitted by applicable law, no full or substantial part of this article may be reproduced, published, translated, adapted, or repackaged without clear author and source attribution and any required permission. Without written consent, it may not be used as material for commercial training, consulting, presentations, datasets, automated content-generation systems, or artificial intelligence model training.
Permissions and corrections: For publication, corporate licensing, training, reuse permissions, or factual correction notices, contact: orkun@orkunak.com
© 2026 Orkun Akçasarı. All rights reserved.
References and Links
The following sources support the article's conceptual framework, identify the author's related management writing, and provide the statutory references underlying the editorial and legal notice. Personal case examples and career data are based on the author's professional archive. The author's related publications are currently available in Turkish.
Selected Publications by the Author
• Orkun Akçasarı - Management Notes (Yönetim Notları)
https://www.orkunak.com/yonetim-notlari/
• Orkun Akçasarı's Company Diagnostic Methodology (Orkun Akçasarı'nın Şirket Okuma Metodolojisi)
https://www.orkunak.com/orkun-akcasari-nin-sirket-okuma-metodolojisi/
• Delegation of Authority and Decision-Making System (Yetki Devri ve Karar Alma Sistemi)
https://www.orkunak.com/l/yetki-devri-karar-alma-sistemi/
• A Full Factory Is Not Necessarily an Efficient Factory (Fabrika Doluysa Verimli Olduğunu Sanmayın)
https://www.orkunak.com/l/fabrika-doluysa-verimli-oldugunu-sanmayin/
• Sales and Production Integration (Satış ve Üretim Entegrasyonu)
https://www.orkunak.com/l/satis-uretim-entegrasyonu-soz-6/
• The Manufacturer Is Not Manufacturing; It Is Financing Everyone (Üretici Üretmiyor, Herkesi Finanse Ediyor)
https://www.orkunak.com/l/uretici-uretmiyor-herkesi-finanse-ediyor/
• Implementing ERP Is Not Digital Transformation (ERP Kurmak, Dijital Dönüşüm Değildir)
https://www.orkunak.com/l/erp-mrp-dijital-donusum/
Project Portfolio and Resource Management
• Project Management Institute - The Standard for Portfolio Management, Fourth Edition
https://www.pmi.org/shop/p-/book/the-standard-for-portfolio-management-%E2%80%94-fourth-edition/00101600601
• Project Management Institute - The Standard for Organizational Project Management
https://www.pmi.org/standards/organizational-project-management
• Association for Project Management - What Is Resource Management?
https://www.apm.org.uk/blog/what-is-resource-management/
Corporate Reference
• Kingfisher plc - About Us - Referenced solely to identify the company and brand in a descriptive context.
https://www.kingfisher.com/about-us
Intellectual Property and Statutory References
• Grand National Assembly of Türkiye - Law No. 5846 on Intellectual and Artistic Works
https://www5.tbmm.gov.tr/develop/owa/kanun_ss.durumu?kanun_no=5846
• WIPO Lex - Law No. 5846 on Intellectual and Artistic Works, Türkiye
https://www.wipo.int/wipolex/en/legislation/details/22507