<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Federico Jarach on Medium]]></title>
        <description><![CDATA[Stories by Federico Jarach on Medium]]></description>
        <link>https://medium.com/@federicoj?source=rss-1e805a78e8b6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*0AavZW_-zdaj5K8HQECIsw.jpeg</url>
            <title>Stories by Federico Jarach on Medium</title>
            <link>https://medium.com/@federicoj?source=rss-1e805a78e8b6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:30:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@federicoj/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Building Sustainable Growth: How Notion Helped Us Scale a Startup Accelerator by 150%]]></title>
            <link>https://medium.com/@federicoj/how-notion-helped-us-scale-a-startup-accelerator-by-150-86daba00f0c7?source=rss-1e805a78e8b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/86daba00f0c7</guid>
            <category><![CDATA[startup-accelerators]]></category>
            <category><![CDATA[no-code]]></category>
            <category><![CDATA[scaling-operations]]></category>
            <category><![CDATA[notion]]></category>
            <category><![CDATA[productivity-tools]]></category>
            <dc:creator><![CDATA[Federico Jarach]]></dc:creator>
            <pubDate>Sat, 01 Mar 2025 23:12:53 GMT</pubDate>
            <atom:updated>2025-03-17T01:24:50.974Z</atom:updated>
            <content:encoded><![CDATA[<h3>Is Your Organization Struggling with Scaling Up?</h3><p>Do you work solo or in a growing organization? Do you find yourself constantly searching for important data, drowning in scattered files, or waiting for teammates across the world to start their workday? Do you wish there was a better way to <strong>streamline workflows</strong>, <strong>increase productivity</strong>, and <strong>scale operations more efficiently</strong>? If so, this might be the read you need. In this post, I’ll share how I leveraged <strong>Notion</strong> — a powerful no-code tool — to transform the way my team worked, and how you can use it to optimize your own operations.</p><h3>The Challenge: Scaling an Accelerator with Limited Resources</h3><p>In early 2023, I joined an accelerator as Program Manager. The organization had launched its first programs just a few months prior, and in many ways, we were like a startup ourselves. It was a public-private initiative with all the complexities that come with it: multiple stakeholders, operations split between the Bay Area and Italy, high expectations, and limited resources.</p><p>It was clear that while the potential was there, <strong>we needed operational systems that could grow with us</strong>.</p><p>Here’s what we were up against:</p><ul><li><strong>A small team working across two continents</strong> — San Francisco and Italy, nine time zones apart.</li><li><strong>Frequent stakeholder updates</strong> — investors, government officials, and partners needed real-time data</li><li><strong>Information spread everywhere</strong> — Google Sheets, PDFs, Slack messages, and emails.</li><li><strong>No centralized system</strong> — team members had to ask each other for basic information.</li><li><strong>A lack of templates and structured processes</strong> — we were just starting, so the first cohorts were built from scratch.</li><li><strong>No tools in place to run multiple programs in parallel</strong> — execution was strictly sequential.</li></ul><p>We needed a <strong>scalable, streamlined solution</strong> to keep up with our growing demands.</p><h3>The Solution: Building a No-Code Operations System in Notion</h3><p>I had experimented with Notion before, but this was the first time I could apply it at scale. Unlike other tools that focused on either task management, documentation, or databases, Notion combined all three in<strong> a single, customizable workspace</strong>.</p><p>Instead of juggling multiple software solutions, I built an integrated operations hub inside Notion, reducing complexity while improving efficiency.</p><p>While a great tool overall, Notion still presents one major challenge: <strong>getting started</strong>.</p><p>With a highly customizable workspace come great possibilities — but also decisions, uncertainty, and a steep learning curve. So the best way for me to approach this was to <strong>start small</strong> — also in part because I was doing this in my spare time, on top of my regular workload.</p><p>I first created a single Notion page that mimicked the structure of an email, showcasing all the ways I thought Notion could meet our needs, and sent it to the team. Once they gave me the go-ahead to start building, the first tools I created were:</p><ul><li><strong>A Notion-based program guide for our next startup cohort</strong>, eliminating scattered PDFs</li><li><strong>A few simply structured, centralized databases to track templates, sessions, and mentors</strong> — replacing endless spreadsheets and email chains</li></ul><p>This <strong>MVP</strong> (Minimum Viable Product) quickly demonstrated its value. The leadership team saw its impact, and <strong>I got the green light to expand</strong> the system.</p><h3>How Notion Enabled Scalability</h3><figure><img alt="A drawing of a little plant growing from a seed" src="https://cdn-images-1.medium.com/max/1024/1*HPnAkCz6ksBQXMQ5kQgPlA.png" /></figure><p>Fast forward to early 2024 — after I had time to <strong>tinker</strong> with Notion and expand our workspace with new databases, processes, and templates — we had transformed our operations in several key ways:</p><ul><li><strong>Parallelized planning</strong> — We could manage multiple cohorts simultaneously instead of one at a time.</li><li><strong>A single source of truth</strong> — Everyone, from leadership to interns, had access to the latest information.</li><li><strong>Automated workflows</strong> — Updating databases, tracking mentor participation, and monitoring session progress became seamless.</li><li><strong>Better cross-continental collaboration</strong> — Teams in Italy and San Francisco could work asynchronously with less delays.</li><li><strong>Real-time reporting</strong> — Generating performance reports became a matter of clicks, not hours of manual work.</li></ul><p><strong>The impact was clear</strong>: In our second year, we increased the number of cohorts by <strong>150%</strong> without expanding the team.</p><p>The work was far from done. I firmly believe that <strong>no system is ever complete</strong> — <strong>only evolving</strong>. Week after week, I continued working alongside the rest of the team, gathering as much <strong>feedback</strong> as possible to <strong>improve the workspace</strong> and <strong>adapting it</strong> wherever feasible to suit each person’s preferred way of working, while preserving core functionalities.</p><h3>What’s Next?</h3><p>This was just the first step. In my next post, I’ll break down <strong>exactly how I built this system in Notion</strong> — including the databases, automations, and workflows that made it work.</p><p>Stay tuned.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86daba00f0c7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>