When Programs Miss the Point: Why Context and Design Matter

Engr. Elaine Macatangay Morales, MPA  |  5 November 2025

A few years ago, an eco-initiative tried to convince small neighborhood stores to switch from sachet products to refill systems. It was a noble idea- reduce plastic waste, empower women entrepreneurs, and promote sustainable consumption. Yet, after a few months, adoption was slow. Not because people disagreed with sustainability, but because the program missed the point: most Filipino families live by the “tingi” mindset. They buy what they can afford for the day- one sachet of shampoo, a few spoonfuls of oil- because their income arrives in the same rhythm. Asking them to shift immediately to bulk buying, even with good intentions, ignored the realities of daily survival.

That case was later redesigned. Instead of imposing total change, the program adapted—retail hubs or eco stores began offering affordable daily refills and small-quantity purchases using people’s own containers. It worked because the system respected the context, though it could be further strengthened by integrating reusable and resealable sachet-like containers to enhance program appeal and participation. The lesson was clear: in program and project development, even the best ideas fail when design outpaces reality.

Seeing the System Behind the Initiative

Programs and projects don’t succeed by accident or by luck. They succeed because their design, implementation, and evaluation are guided by systems thinking- anchored in purpose, context, and coherence. A program is a structured collection of projects aligned toward a common goal, while a project is a defined, time-bound initiative producing a specific outcome. When these two are treated as isolated activities rather than interconnected components of an organizational system, the result is fragmentation, many moving parts but little movement forward.

Under ISO 9001:2015 (Quality Management System Standards), organizations are required to understand their context (Clause 4), align actions with strategic direction (Clause 6), and use evidence-based decision-making (Clause 9). These principles aren’t exclusive to manufacturing, they are universal. They remind us that every program should come from a clear mission and vision, supported by coherent objectives and targets, not from ad hoc or politically convenient decisions.

Unfortunately, in many institutions- public, private, or nonprofit- programs are sometimes driven by visibility, not viability. A new project gets approved because it sounds innovative or fits a trend. A partnership is launched because it looks good on social media. Budgets are rushed to “use the funds” rather than address systemic needs. When this happens, what gets lost is not just efficiency, but integrity of purpose.

Feasibility Is More Than Funding

Feasibility is often mistaken as merely a question of financial capability. In truth, it is also about fit- whether a program’s design can actually work within its context. A well-written proposal with a promising budget can still fail if it overlooks cultural behaviors, resource realities, or social dynamics.

The eco-store example worked the second time around because it recognized that success depends on design compatibility. The mechanics- refill systems, daily affordability, and women-led stores- aligned with the way people live and earn. Feasibility, then, is not just a matter of funds but of design logic: Are the objectives attainable given the environment? Are the beneficiaries ready and able to participate? Are we solving the right problem?

This mirrors project identification and concept development principles in public administration: idea generation, screening, pre-feasibility, and stakeholder consultation. Each step tests whether the initiative is realistic and responsive. In quality systems, it is similar to risk-based thinking- anticipating what could go wrong and planning accordingly.

This same principle applies to startups. Many promising ventures fail not because their products are bad, but because they solve the wrong problem or target unready users. Market and user readiness, contextual understanding, and behavioral insight are as critical to startup success as capital. Of course, business feasibility is a separate discipline but the systems logic behind it is universal.

Alignment, Not Accumulation

One of the silent killers of organizational effectiveness is the creation of disjointed programs- an assortment of projects competing for attention and resources, none strategically integrated. A well-governed organization designs “mother programs” with interlinked projects, each reinforcing a shared mission.

For example, a STEM institution might have a “STEM Talent Development Program” composed of scholarships, teacher training, student capacity building, and research projects- each distinct but complementary. Compare that with an institution running separate, unrelated activities and probably under different departments, with no unifying goal. The first operates as a system; the second, as a smorgasbord.

The distinction reflects Clause 5 (Leadership) of ISO 9001, which calls for leadership commitment and alignment of quality objectives with strategic goals. Programs that lack alignment may still spend but they seldom sustain.

Accountability and Evaluation

When partnerships are formed without clarity of roles, collaboration can quickly devolve into confusion. Systems thinking demands that partnerships be strategic, not ceremonial. In a well-structured program, responsibilities are defined, communication lines are established, and accountability mechanisms are embedded in the design.

Equally important is evaluation. Many programs end with reports that list activities and activity counts such as number of attendees, not real outcomes. But as quality management reminds us, performance must be measured through metrics that matter: efficiency (resource use), effectiveness (goal attainment), and impact (sustained change). Under ISO 19011 (Guidelines for Auditing Management Systems), internal audits serve not as fault-finding exercises but as learning mechanisms to improve systems. The same should hold true for public and social programs. Evaluation is not a postscript; it is a feedback loop essential for improvement.

Systems, Not Symbols

Every organization, whether government agency, private company, or NGO, wants to make a difference. But intention must be matched with intelligent design. Programs and projects are instruments of systems change, not just symbols of goodwill. When they are built on solid data, risk awareness, and strategic alignment, they create ripples of real transformation. When they are built on impulse or imitation, they create noise.

Good systems protect not only resources but also trust- the trust of taxpayers, customers, donors, and communities. And in the end, that is what truly sustains an organization’s purpose.

Because systems thinking reminds us: when programs miss the point, it’s often because they missed the system.