Framework

    Building Ecosystems

    A framework for designing organizational ecosystems that grow with purpose, illustrated through the Finnish startup scene. Originally published across two editions of Just Thoughts.

    Too long; did read

    • Building Ecosystems is a four-step framework for designing organizational or startup ecosystems that grow with purpose.
    • Every ecosystem needs a Line of Purpose that reflects the lifecycle it supports.
    • Ecosystems are built by people, not institutions. Trust and active participation drive the system.
    • Four rules govern healthy growth: fit the purpose, avoid attention overlap, dare to build better, and mind timing and region.
    • Illustrated through the Finnish startup ecosystem, but applicable to any community, industry, or creative scene.

    The Four Steps

    Click each step to explore how ecosystems are built from purpose to focus.

    🧭

    Define the Line of Purpose

    Why the ecosystem exists

    Every ecosystem serves a purpose that gives it a reason to exist. Just as an ecosystem in nature exists to preserve life, an ecosystem in business exists to preserve something specific. The 'line of purpose' reflects the lifecycle of its core unit, whether that is a startup, a creator, or a community member, from beginning to end.

    Key Points

    • Articulate the lifecycle your ecosystem supports (e.g., the startup journey from idea to exit)
    • Ensure every player in the ecosystem can see how they contribute to the whole
    • Ecosystems are built by people, not institutions. Relationships and trust drive the system
    • If you change everyone in an organization, ask whether it is still the same organization
    Example

    The Finnish startup ecosystem's line of purpose is to create more startups. Every initiative, from Aaltoes inspiring students to Slush connecting founders with investors, maps to a stage in that lifecycle.

    The Four Rules

    Principles that govern healthy ecosystem growth.

    1

    Always create a project that fits the line of purpose.

    If a project doesn't serve a clear need in the lifecycle your ecosystem supports, it won't get organic support from the community.

    2

    Don't build a new community if it doesn't bring new people or retain drop-outs.

    People have a finite amount of time and attention. Competing for the same audience dilutes the total impact of the ecosystem.

    3

    If you can build something better and are willing to fail trying, build it.

    Sometimes rule two must be broken. If you genuinely believe you can improve on what exists, go ahead. The builders of these new endeavors become the ecosystem's heroes.

    4

    Be mindful of timing and region.

    Timing and location give space for creation. Two events in different seasons or cities can coexist; two events targeting the same audience at the same time cannot.

    The Journey

    How an ecosystem evolves from purpose to focused maturity.

    🧭
    Step 1

    Define the Line of Purpose

    Why the ecosystem existsEvery ecosystem serves a purpose that gives it a reason to exist.

    🗺️
    Step 2

    Map the Needs

    Start at the beginning of the lifecycleDon't get ahead of yourself.

    🌱
    Step 3

    Grow and Push Forward

    Expand with new endeavors and playersAs the ecosystem matures, build new endeavors that push it forward or include new players that fit the lines of purpose.

    🔍
    Step 4

    Drill Down to Find Focus

    Uncover sub-lifecycles when it gets crowdedWhen the ecosystem gets crowded, drill down on the purpose line to find sub-lifecycles inherent to the main one.

    Does this resonate?

    Would love to hear why — what landed, what didn't, what it stirred up in your own work.

    Share your story

    Unlock more

    Don't miss future writing — become a paid Substack supporter and keep this going.

    Become a supporter

    Frequently Asked

    Common questions about the Building Ecosystems framework.

    From the Conversation

    Anecdotes from a wide-ranging discussion with Aape Pohjavirta on ecosystems, memory, and belief.

    Belief Preceded Capital

    "Apple's early story wasn't about genius alone — it was about someone (Mike Markkula) who believed early, before certainty or strategy decks existed. Systems don't start with optimization; they begin when they are believed in."

    On why ecosystems need believers before they need investors.

    Pattern Memory over Thought Leadership

    "Aape isn't a 'thought leader' — he's a carrier of memory. The asset isn't opinion; it's pattern recognition across decades of watching technology shifts, hype waves, institutionalization, and forgetting."

    On the role of ecosystem elders who stay in the game long enough to see cycles repeat.

    When Radical Ideas Succeed

    "Once something works, it risks becoming an event, a format, a machine — rather than a living experiment. The asset Slush once had wasn't scalable. It was permission to be weird before it worked."

    On the lifecycle trap of successful ecosystem initiatives.

    Prefer the full narrative? Read the original versions on Just Thoughts

    What to read next