<?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 Daniel Lazarovitch on Medium]]></title>
        <description><![CDATA[Stories by Daniel Lazarovitch on Medium]]></description>
        <link>https://medium.com/@daniellazarovitch?source=rss-d20062b4a0af------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*KcNYSPSzGSrNz4bimB3BLA.png</url>
            <title>Stories by Daniel Lazarovitch on Medium</title>
            <link>https://medium.com/@daniellazarovitch?source=rss-d20062b4a0af------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 20:35:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@daniellazarovitch/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[How We Established A Frontend Strategy]]></title>
            <link>https://medium.com/@daniellazarovitch/how-we-established-a-frontend-strategy-a304738722e2?source=rss-d20062b4a0af------2</link>
            <guid isPermaLink="false">https://medium.com/p/a304738722e2</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[code-architecture]]></category>
            <category><![CDATA[code]]></category>
            <dc:creator><![CDATA[Daniel Lazarovitch]]></dc:creator>
            <pubDate>Sun, 26 May 2019 19:54:03 GMT</pubDate>
            <atom:updated>2019-05-28T11:36:17.171Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mWBJeBGPpAvP1NsZwCL1Yg.jpeg" /><figcaption>Image from <a href="http://rawpixel.com/">rawpixel.com</a></figcaption></figure><p>When I started as frontend architect in 2018, one of my first tasks was to deliver a plan that showed how we could modernize our codebase. A plan that showed the current state (where we were), the future state (where we want to be) and most importantly, a plan that guarantees incremental movement.</p><p>The plan of modernizing our codebase soon enough took an unexpected turn as it quickly grew to become the foundation of the way we work, of the way we make decisions, of technology alignments, of our culture. It clarifies the relationship between technology and product.</p><p>Looking at the entire journey, modernizing our codebase was actually the trigger to something bigger, something that we as engineers desperately wished for but could not put our finger on, namely a Frontend Strategy.</p><h3>Why do we even need a Strategy</h3><p>Well, you don’t need to have one but at the same time you probably should.</p><p>If you look at a codebase and the amount of engineers working on it daily, the more engineers working on it the more diversion your codebase is exposed to and more the alignment needs to be done.</p><p>A codebase that is constantly exposed to diversion and technical alignments, does not let you plan and achieve any goals under conditions of uncertainty and clarifies close to nothing about the long term goals.</p><blockquote>A strategy is a plan of actions designed to achieve a long-term or overall aim.</blockquote><p>Therefore we saw the potential of creating a Frontend Strategy, which naturally will introduce long term goals such as modernizing our codebase but also set the framework for future decisions.</p><p>When we are unified in regards to our long term goals or overall aim we can let creativity shine and build something new.</p><h3>First Steps</h3><p>The first step is to ask the obvious question, what are our long term goals?</p><p>To be able to answer that, we need to do two things. Firstly, refining “long term goals” into a more digestible questions.</p><p>Secondly, we need to cast a wider net, which means to not only concentrate on the technology aspect but also on the product.</p><p>I interviewed engineers about the pain-points of the codebase, how they would like to use it, how easy it is to on-board a new developer, how well a documentation process we have, how a code review process is conducted.</p><p>As the product is a big part of the answer, I went to Scrum Masters, Product Owners and Content and asked about how fast we can validate a feature, how we measure success and if technology was not a blocker for them, what kind of products they would like to build.</p><p>The feedback was great!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F5wWf7GW1AzV6pF3MaVW%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Feditingandlayout-the-office-high-five-5wWf7GW1AzV6pF3MaVW&amp;image=https%3A%2F%2Fmedia2.giphy.com%2Fmedia%2F5wWf7GW1AzV6pF3MaVW%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="251" frameborder="0" scrolling="no"><a href="https://medium.com/media/4390e4ee60076108b0ace6cdc4f429c6/href">https://medium.com/media/4390e4ee60076108b0ace6cdc4f429c6/href</a></iframe><p>I got a pool (aka: <em>the pool</em>) of thoughts, ideas, wishes, views and concrete action points to work with!</p><h3><strong>The Big Picture</strong></h3><p><em>The pool</em> is a raw, priceless set of data about everything from the way we work to how things should be in a perfect world.</p><p>“I want a clean codebase”, “I would like to be able to upgrade and work with the latest libraries”, “Could be nice to deliver a feature, a fix to a customer in seconds or minutes” — does this really show the big picture or are they pieces of something greater? — clearly the latter.</p><p>Seeing the big picture requires refinement of <em>the pool</em>. The refinement process is mainly done with the help of lead developers, head of product owners and agile coaches.</p><h3><strong>The Frontend Strategy</strong></h3><p>We came up with the following strategy as we felt it gives the opportunity to focus on our directions in the best way. For us as an engineering department it will, therefore, help us develop the right targets, goals and focus on the overall effort.</p><p><strong>A better experience for the customer and a better experience for the developer</strong></p><ul><li>Minimize Time to Market</li><li>Maximize Productivity</li><li>Automation of Process</li><li>Clean Codebase</li></ul><p><strong>Technology as a product enabler</strong></p><ul><li>Our technology needs to support product growth</li><li>Our technology needs to be prepared for futuristic product directions</li><li>Our technology needs to support rapid validation of product</li></ul><p><strong>Culture, culture, culture</strong></p><ul><li>Contribute to the Tech Community</li><li>Supplementary education</li><li>Knowledge sharing &amp; Discussions</li><li>Having Fun</li></ul><h3><strong>Dividing engineers into well defined initiatives</strong></h3><p>Now that we have our Frontend Strategy lined up, we are still missing one thing.</p><p>How can we connect our strategy to address <em>the pool</em> of thoughts, ideas, wishes and views.</p><p>Clearly some sort of governance with well defined context needs to be established so we can execute and measure success.</p><p>We choose to take another look at our codebase and seek an answer “What makes our codebase as a whole?”.</p><p>The result was to kick off initiatives where each initiative moves the strategy in its own direction and together brings forward the strategy as a whole.</p><p>The initiatives we came up with:</p><ul><li>Foundations/DevOps — Provide enablers at a Platform level</li><li>Unified Experience — Unifies the user experience across products</li><li>React — Provides best solutions for modernizing the Codebase</li><li>Insights Maturity — Provides tooling and best solutions on how teams address analytics</li></ul><h3>Planning of Strategy and Milestones</h3><p>So far we have our strategy in place and initiatives with a well defined context that can execute and measure success.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FxTiTniJxdAPEjeCkVi%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fmlb-usa-r-xTiTniJxdAPEjeCkVi&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FxTiTniJxdAPEjeCkVi%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/5c1fae5a04184c230d0f37c1b637438c/href">https://medium.com/media/5c1fae5a04184c230d0f37c1b637438c/href</a></iframe><p>Based on the process that have been done so far and meetings and alignments that have been done at a guild and tech sync level we chose to focus on the following: Introduce CI/CD pipelines, modernizing our codebase, shift to headless CMS and introduce a Pattern Library .</p><p>After each of the initiatives came up with a road map and milestones and after all roadmaps were refined, aligned and prioritized, we ended up with the following EPICS:</p><ul><li>Migration to Headless CMS — Foundation/DevOps</li><li>Investigate on CI/CD pipelines (focus on CircleCI, Jenkins, Travis) — Foundation/DevOps</li><li>Establish a Pattern Library — Unified Experience</li><li>Styling across products — React &amp; Unified Experience</li></ul><h3>From Roadmap to Tasks</h3><p>We can go into an even higher resolution and see how the EPICS are converted into actionable tasks:</p><ul><li>Upgrade on-premise servers to new version of headless CMS — Foundation / DevOps</li><li>Enable NPM packages — Foundation/DevOps</li><li>Prepare the migration of teams to the new CMS setup — React &amp; Foundation / DevOps</li><li>CSS Modules — React &amp; Unified Experience</li><li>Components Library — Unified Experience</li><li>Sharing Styles (Figma to SASS variables) — Unified Experience</li><li>Upgrade react version to latest and utilize its modern features — React</li></ul><p>With these initiatives placed and kicked off we can now start measuring success.</p><h3>Keeping it all together</h3><p>Initiatives are autonomous and run their own meetings and roadmap, but that does not mean they can run free in the wild.</p><p>Each initiatives have a driver or co-drivers and these drivers meet together with other initiative’s drivers, architects and engineering managers once a month so we can avoid diversion from goals and promote alignment of the general architecture, technical roadmaps and overall Frontend Strategy.</p><p>We communicate our updates at the Frontend Guild meetings and Technical Syncs, so we can make sure all of the engineers are updated and on board.</p><p>We take advantage of these forums to demo and show case possible directions and collect any feedback that can arise so we can refine ourselves within an initiative as well.</p><h3><strong>Final Thoughts</strong></h3><p>Having a Frontend Strategy turned out to be beneficial for our engineers in the sense of transparency and communication and boost the confidence and clarity of where we are going as a department.</p><p>It also created a clear communication channel with product owners and other business stakeholders where they can come and give input regarding current / future business requirements and get answers that might help shape future product direction, e.g.: “Are we ready for Desktop &amp; Mobile development?” and “How fast can we do a POC?”.</p><p>If you are now wondering how many meetings we have? that’s fair!</p><p>We keep it at a minimum, bi-weekly meeting per initiative and a monthly with architects and other engineering managers. Each “sync session” can go anywhere from a quick 30 min to maximum 1 hour.</p><p>Each initiative have their own Slack channel to keep communication going and we use the polls feature for quick decision making and much more.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F24FQHGLzRxw5BsGX6G%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Ffallontonight-jimmy-fallon-tonight-show-fist-pump-24FQHGLzRxw5BsGX6G&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F24FQHGLzRxw5BsGX6G%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="314" frameborder="0" scrolling="no"><a href="https://medium.com/media/77f2037b275839876ea3137f0e521715/href">https://medium.com/media/77f2037b275839876ea3137f0e521715/href</a></iframe><p>As product moves forward, we are being asked to supply the right platform and supportive tooling and we are happy to face the new challenges, whatever they might be, with great pleasure.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a304738722e2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>