Impact Project Design

A practical guide for designing oikos projects that actually change something

A quick story before we start. A few semesters ago, a chapter (let's not name names) spent six weeks planning a “Sustainability Week.” Five events, a great Instagram grid, a budget spent down to the last euro. Attendance: solid. Vibe: great. Six months later? Nobody could say what was actually different because of it. Sound familiar? This guide exists so that doesn't have to be your chapter's story.

Introduction

Every chapter runs activities. Far fewer chapters create lasting impact. This guide helps you design projects that move beyond “we hosted an event” toward “we changed something, for someone, and it's still changing things.”

🧭 Here's What You'll Walk Away With

• A way to find a real problem worth solving - not just an event idea looking for a justification

• The mindset shift from “running activities” to “creating meaningful change”

• A simple, repeatable design flow you can apply to your next project, starting tonight

• Tools for building the right team around your project, piloting smart, and making sure it survives your own graduation

What Is Impact Project Design?

It's the practice of designing a project backward from the change you want to create, instead of forward from “what event should we run.” It covers everything from spotting a real problem, to co-designing the solution with the people affected, to building a project that's measurable and built to last beyond your own board term.

It applies any time your chapter is about to launch something - a workshop, a campaign, a partnership, a long-term initiative - not just for big flagship projects.

Why Does This Matter for oikos Specifically?

Because oikos chapters are run by students with one- or two-year terms, a packed academic calendar, and a turnover problem most companies would never survive. That combination makes it dangerously easy to default to “let's just run the workshop we ran last year” - it's familiar, it's safe, and it fills the calendar.

The problem: familiar isn't the same as impactful. oikos's whole reason for existing is to develop future leaders who integrate sustainability into business and society - and you don't build that muscle by repeating events. You build it by learning to diagnose real problems and design real solutions, the exact skillset this guide is meant to train.

How: From Idea to Impact - The Funnel

Think of project design as a funnel. You start wide - exploring problems and people - and narrow step by step until you have something specific, fundable, and measurable.

Step 1 - Start With a Real Need, Not an Event Idea

Stop asking:

❌ “What event should we organise?”

Start asking:

✅ “What impact do we want to create, and for whom?”

Explore the problem through four lenses:

Lens	Ask	Examples
Community	What issue exists locally?	education gaps, financial literacy, inclusion barriers
Sustainability	What challenge exists?	waste, climate awareness, unsustainable behaviour
University	What challenge exists on campus?	low engagement, weak sustainability culture, lack of ESG awareness
Stakeholder	Who can help and who is affected?	students, NGOs, faculty, communities, partners

Helpful to ask: Who is affected, why does it matter, and what would meaningful change actually look like?

Step 2 - Design With, Not For

This is, in our opinion, the single most important idea in this entire guide. Strong projects are co-created, not delivered.

Before launching anything, ask:

• What do people actually need (not what you assume they need)?

• What has already been tried - and why did it work or fail?

• What barriers exist?

• What would success look like for them?

• Have you talked to alumni or past chapter leaders? Their experience is gold - just remember what worked before may not work today.

❌ Weak: “Let's donate books to the local school.”

✅ Stronger: “Let's find out whether what's actually missing is mentorship, digital access, or teacher support - then design around that.”

People should walk away from your project feeling consulted, involved, and respected - not “managed.”

If you want a 6-minute gut-check on this exact trap, watch Ernesto Sirolli's TED Talk "Want to help someone? Shut up and listen" - it's the talk that turned “design WITH not FOR” into a one-liner people actually remember.

Step 3 - Think Beyond the Event

Not every well-attended event creates impact. Compare:

Event Mindset	Impact Mindset
“Let's host a sustainability workshop.”	“Students lack sustainability literacy, so let's design something that builds awareness and action.”
One-off event	Ongoing initiative
Attendance focus	Outcome focus
Awareness only	Behaviour change
No follow-up	Continued engagement

Step 4 - Keep the Change Logic Simple

Before launching, be able to answer in one breath: how exactly will this create change?

Want to go deeper? This simple chain is a lightweight cousin of a Theory of Change - a tool many established nonprofits use to map exactly how their work leads to long-term change. You don't need the full version for most chapter projects, but if you're designing something ambitious or multi-year, this nonprofit guide to Theory of Change is a genuinely useful, non-academic starting point. (Concepts like Impact Logic and Regenerative Design live in the same family - worth a search if your project is ecosystem-scale, but not essential reading for a first project.)

Step 5 - Build the Right Ecosystem

Strong projects are collaborative by design. Map your people into two rings:

Ask the team: Who is essential, and who amplifies our impact?

(Related Toolbox section: see Partnerships for a deeper dive on managing these relationships long-term.)

Step 6 - Start Small, Learn Fast

Avoid the temptation to scale immediately - it's the fastest way to burn your team out and your credibility with it.

Recommended approach: Pilot → Learn → Improve → Scale

• ❌ Launch across 20 schools immediately

• ✅ Pilot in 1 school → improve → expand

💡 What is the smallest version of this project we could test first?

Step 7 - Design for Measurement, From Day One

Don't bolt measurement on at the end - bake it in before launch.

Ask:

• What would success look like?

• How will we know if change happened?

Project Type	Example Indicator
Awareness	Knowledge gained (pre/post surveys, quizzes)
Sustainability	Waste reduced (kg tracked, recycling rate)
Community	Beneficiary feedback (feedback forms, satisfaction score)
Behaviour	Actions adopted (number of commitments, behaviour tracking)

Full deep-dive: see How to Assess Impact for the complete framework on turning these indicators into a real impact story.

Step 8 - Design for Continuity

Ask:

• Can future teams continue this?

• Is the process documented?

• Can someone who's never run this project pick it up and replicate it?

Strong oikos projects outlast leadership transitions - that's what separates a project from a one-off favour to your CV.

Related Toolbox sections: Handover Processes · Purpose-Led Leadership · Vision & Strategy

Step 9 - Reflect and Share, Every Single Time

After every project, gather the team and ask:

• What worked well?

• What didn't?

• What surprised us?

• What would we improve?

• Could another chapter replicate this?

For the full reflection framework (including how to turn this into a documented “best practice”), see the Learn, Reflect & Share section of How to Assess Impact - no need to repeat it twice in your head, it lives there.

Summary

Strong oikos projects don't start with “what should we organise” - they start with a real need, get designed with the people affected, build the right ecosystem of support, get piloted before they get scaled, and are built to survive your graduation. Measurement isn't an afterthought - it's baked in from day one.

🎯 Main Takeaway

Success isn't “how many events did we organise?” - it's “what meaningful change did we create, and will it still be creating change after we're gone?”

💡 Tips & Tricks - Try This Tomorrow

• Run the “donate books” test on your current project idea: are you assuming what people need, or have you actually asked them?

• Call one alum from your chapter this week and ask what they wish they'd known before launching their first project.

• Write your project's one-sentence change logic (Problem → Activity → Reach → Outcome → Impact) on a sticky note and put it where your team will see it at every meeting.

• Pick one project currently “stuck at idea stage” and identify the smallest possible pilot version you could test in the next 4 weeks.

• Before your next kickoff meeting, draft a one-page “who's core, who's auxiliary” map - it takes 10 minutes and saves weeks of confusion later.