Every frontend trend list said the same thing, so she started from the why
Two December 2020 trend articles named the same four frontend trends: progressive web apps, single page applications, motion design and TypeScript, just shuffled. Asked to write a management summary on frontend strategy, Maria Korneeva, Frontend Tech Lead at Aleri Solutions, found that copy-paste consensus offered no real guidance. So how does a mid-sized company pick frontend technologies it can justify to management and to its clients?
Get a why-first method to scope, assess and document a frontend tech stack that holds up
Maria Korneeva, Frontend Tech Lead at Aleri Solutions, explains how she built a frontend strategy for a mid-sized IT company after finding trend articles useless. She argues for fitting the strategy into the company's existing strategic framework, defining assessment criteria before choosing frameworks, documenting choices in a technology radar, and adapting the approach when frontend skills are sold as consulting.
“So consistency is good, but I strongly sense the copy paste skills and that made me even more insecure how I'm supposed to choose.”
“And once you have this, once you know what's important for your company, then you can choose technologies and then you can overcome this framework hype.”
What you will learn
Align a frontend strategy with the company's existing vision, mission, HR structure and business canvas instead of starting from scratch.
Replace vague selling points like a highly motivated team with provable facts such as reference projects, partner contracts or certifications.
Define technology assessment criteria by interviewing developers, architects, scrum masters and product owners before choosing any framework.
Document technology choices in a technology radar and segment frontend competence into groups such as essentials, fancy sites and powerful apps.
Adapt the strategy for consulting work by weighing client tech stacks, legacy cash cows and the need for strong communicators.
Key takeaways from the speaker
Focus on business needs, not frameworks
Segment your frontend competence
Pair your team competence with career level
Base your USP on hard facts
Details
Level
Intermediate
Format
Talk
Technical depth
Introductory technical
For
Senior individual contributor, People manager
Length
17:06
Published
June 2021
Questions this talk answers
Can annual web development trend articles guide a frontend strategy?
Not reliably: the speaker found December 2020 articles repeating the same list in different order. She recommends defining your own reasons and assessment criteria first.
Where should a frontend strategy start?
With the company's existing strategic framework: vision, mission, strategy, HR structure, business canvas and SWOT analysis, so the frontend strategy fits in rather than starting from scratch.
How do you build criteria for choosing frontend technologies?
Talk to developers, architects, scrum masters and product owners about pain points and features, then cluster the input into requirements such as customer and developer experience, technology as product enabler and cultural fit.
How does a frontend strategy differ for a consulting company?
Frontend skills become the product, so client tech stacks and needs shape the criteria, there is a trade-off between cash cows and state-of-the-art technologies, and communication skills matter as much as coding.
How often should a frontend strategy be revisited?
The speaker suggests reviewing the technology radar quarterly, the assessment criteria yearly, and the whole strategic framework when needed.
About this talk
Predicting future is hard, yet every December we see plenty of blogs with titles like “Web Development Trends <put-next-year-here>”. Are they reliable enough to use them in your business forecast?
In this talk I’m going to share my insights in crafting frontend strategy for a mid-sized IT company. You will learn about my way to tackle velocity and diversity of frontend technologies at the enterprise level. I want to discuss with you the “whats”, “whys” and “hows” of strategising, including some struggles that I faced, e.g. the soft "border" to other tech topics such as API & services, DevSecOps etc…
Challenging? Someone said challenging? So, let's roll up the sleeves!
Frontend's reputation problem and the people factor (53 s)
When frontend strategy becomes product strategy (55 s)
Welcome to my talk, crafting frontend strategy. My name is Maria Korneeva and I'd like to briefly introduce myself. As Anna said, I'm a frontend technology lead at Aleri Solutions, a company based in Cologne, Germany. In my free time, I like to write articles for ng-conf, so feel free to check it out. And if you have any questions or you like to connect, feel free to drop a line via email, LinkedIn or Twitter. But let us start with the talk. What's the struggle? Last year I was appointed as frontend technology lead and I was given the task to prepare management summary on frontend strategy. So what did I do? I went Googling. I discovered that there are just few links with tips, so I was left without any real help for this.
Speaker 1: So then I decided to check out the tendencies from current trends and how I'm supposed to choose the state of the art technologies or future technologies for frontend. Speaker 1: It was December 2020 and there were a lot of websites with some recommendations. One site, for example, said there's going to be progressive web app and single page applications and motion design and TypeScript.
Speaker 2: Another website said it's going to be TypeScript, motion design, progressive web apps and single page applications. So consistency is good, but I strongly sense the copy paste skills and that made me even more insecure how I'm supposed to choose. If it isn't the truth. What it's written in those articles? Should I follow those recommendations? Speaker 1: So this is when the idea of this talk was born. I decided to share my insights on the way to the frontend strategy that I had to prepare for my company.
Speaker 1: To share with you anything that I've learned through this process. Let us start. I'm going to cover the connection between strategic framework of your company and the frontend strategy. Speaker 1: How some some approaches and techniques, how you can make sure that you choose the right technologies and the difference between frontend technology for your company like internal frontend strategy and the strategy in the case if you are a consulting company. So you have to accommodate some other requirements in the strategy too. Let us start.
Speaker 1: Let's have a look at the overall company. Usually, unless you start registering your startup, you wouldn't start from scratch. So in your company there, there is a vision or it should be, there should be a vision, mission and strategy for the whole company, which means that you have to fit in. For example, if your HR has the pyramid as the.
Speaker 1: Overall structure, meaning more associates colleagues at the bottom and few just a few senior colleagues, then you have to align your needs within this set sheet too, or you have to negotiate with your colleagues. Speaker 1: If you need more senior people than and less associates, but the positive side of this is that you don't start start from scratch.
Speaker 1: So you there might be some documentation on the strategy so that you can align your front and front end strategy within it. Speaker 1: For example, you can use business canvas. Speaker 1: There you can find the information about USB unique selling proposition and the target customers. Speaker 1: I will cover this later once we're talking about consulting other companies, but this is certainly the information that you can reuse in your front end strategy.
Speaker 1: I went on with saying that we are the highly professional team, highly motivated client oriented. Speaker 1: However, my sparing partner said that I cannot prove this, so I'd better go with some fact based information. Speaker 1: For example, I'd say you should go. Maybe you should go with industry knowledge and then you can provide reference projects for this.
Speaker 1: Or maybe you cover you can provide end to end support for your products because the skill set in your company allows you to do so. Speaker 1: You can prove it. Speaker 1: Maybe your your offer is unique due to your corporations, so you can prove it by providing the contracts with your partners. Speaker 1: Or maybe if you still want to go with the highly skilled team, you can provide some certifications to stay at the point.
Speaker 1: Another piece of information that you can reuse could be this what analysis strengths, weaknesses, opportunities and threats. Speaker 1: I'm not going to go into details about this type of analysis. There are plenty of information on this, but rather some topics that I covered in my SWOT analysis to prepare for the front end strategy that you might reuse for your company.
Speaker 1: First of all, the differentiation between front end and back end. So it's really hard to say where front end stops and back end begins. And if there is a back end technology, how do you differentiate? How do you divide your responsibilities? Speaker 1: Or if your company has full stack developers, how do you? Well, how do you split your this person into two between front end and back end?
Speaker 1: Speaking about competitions, you might mind freelancers because this is a huge part of highly skilled professionals that are out there in the market that quite often take over the front end developer tasks. Speaker 1: If you're a middle sized company like we are, you probably should look at price driven agencies or offshore colleagues because or offshore companies because they are more flexible in price and time.
Speaker 1: So you have to come up with some focus on your projects to to make the best out of it. Speaker 1: Speaking about the chances, front end is becoming more complex. Speaker 1: So your customers are relying more and more on external expertise, which is a chance for you for your company or might be the chance on the other side.
Speaker 1: There is a rise of low code platforms. So some companies might some customers might decide to code or to to create their websites themselves, which is definitely a threat. Speaker 1: Another threat is that there is actually no established certification for front end like we have some certificates for our architects. Speaker 1: We have several certificates for back at like Java or AWS or whatever technology.
Speaker 1: But for front end there is nothing, at least not that I know, which is really widely spread. Speaker 1: And maybe except for Google developer expertise experts, but that's this another story. Speaker 1: And the last but not least, the more and the focus of software development moves away from web development. Speaker 1: This is an unpleasant news, but now IoT, blockchain or machine learning are rather the hot topics and web development as well as mobile development are rather seen as enablers, which is still important.
Speaker 1: But this is a different arguing position within the company if you have to negotiate for budget. Speaker 1: So what were the challenges that I faced during preparing when preparing my front end strategy? Speaker 1: First of all, as I mentioned, front end is becoming more and more powerful. Speaker 1: So it's really hard to say where is what is the scope of of my role?
Speaker 1: What's the scope of this strategy? Speaker 1: And it's really hard to do to divide to to differentiate it from different from other technologies. Speaker 1: For example, are the static site generators part of front end are hybrid mobile apps part of front end since they are running in the browser. Speaker 1: So what is the scope of my role?
Speaker 1: What is the scope of the strategy? Speaker 1: And then this infamous for a framework card every single week. Speaker 1: There is a new frame front end framework. Speaker 1: So you have to. Speaker 1: What is top? Speaker 1: What is flop? Speaker 1: How do you stay up to date? Speaker 1: And how do you figure out?
Speaker 1: What's the real thing? Speaker 1: What's the next big thing? Speaker 1: Those are again the two questions that you have to answer in your front end technology Speaker 1: As I mentioned, the front end front end development or web development is no longer in focus. Speaker 1: So it's harder for you to to negotiate to ask for more people for more budget if the focus moves towards cloud towards IOT or other stuff connected to this.
Speaker 1: This is the the role or the reputation of front end development in German. Speaker 1: There's a word called pixel shop, meaning someone who is moving around pixels, which is kind of irrespectful towards front end or ironic towards front end developers. Speaker 1: So you have to do some marketing within your company to to prove that front end developers are as killed as back end and they're doing as complex work job as other developers do.
Speaker 1: Sometimes it might be the case. Speaker 1: It's not only about the technology. Speaker 1: So you have to think about developer experience. Speaker 1: You have to train your people. Speaker 1: And this is actually the most valuable aspect. Speaker 1: It's it's the thing that make can can disrupt all the whole brilliant idea of the best technologies that you've chosen.
Speaker 1: And another layer layer of complexity is that you have to think about technologies, not only for yourself, for your company, but also for your clients, if you doing some consultancy work. Speaker 1: So but the overall idea of it is that you first have to concentrate on the why question or the reasons, the assessment criteria for the technologies.
Speaker 1: And once you have this, once you know what's important for your company, then you can choose technologies and then you can overcome this framework hype. Speaker 1: You know why you've chosen those technologies. Speaker 1: You've made a conscious choice in this case. Speaker 1: So speaking about this why question, let us have a look at one of the approaches.
Speaker 1: I've discovered this case study. Speaker 1: I've provided a link below where the author did exactly this. Speaker 1: First of all, he talked to his people like no front end strategy will come outside. Speaker 1: You have to base it on your your company's needs. Speaker 1: Talk to your developers, talk to your architects, ask them about their pain points, about the problems with the code base, the process of code review, all this stuff.
Speaker 1: Talk to your scrum master, talk to your product owners about features, feature validation, feature release, big dreams if technology was no limit. Speaker 1: And once you have this information, you should refine this pool of thoughts structure. Speaker 1: Those are the three elements in here. Speaker 1: With the main goal to come with some clusters of requirements.
Speaker 1: In this case, which is quite similar to ours, the author came out with three clusters. Speaker 1: The first one is the custom experience and developer experience. Speaker 1: Technology as product enabler and cultural fit. Speaker 1: So we want to have a technology that minimizes time to market. Speaker 1: We want to maximize productivity.
Speaker 1: We want to automate our processes and we want to maintain clean code base. Speaker 1: We want to have a technology that supports product growth now and in the future. Speaker 1: And of course, there should be a cultural fit in our company. Speaker 1: Once you have this requirements framework or assessment criteria, you can move on and assess technologies and choose which one you're going to keep.
Speaker 1: For this, there's another technique I could recommend called technology radar. Speaker 1: If you're not familiar with this, go on and read the article that I provided below. Speaker 1: I'm not going to go into much detail on this, but this is a technique that allows you to document, assess and structure your technology stack. Speaker 1: You can decide which technologies you want to avoid, which you're going to experiment with, or maybe some that you want to focus on and learn more about them and the ones that are already using.
Speaker 1: So you can go even further in structuring and clustering your front end technologies into some groups. Speaker 1: This is an example that I use in my company, for example, and the powerful apps, fancy sites, all rounders, helpers and essentials. Speaker 1: And I mean by this the following. Speaker 1: Of course, you need to cover the essentials, providing responsive, accessible, cross-browser and device compatible apps.
Speaker 1: But then you can differentiate even further by saying, if you're going to build bigger apps or more complex apps, you might want to go with Angular because this framework is more suitable for this. Speaker 1: If your focus is on beautiful microsites, you'd rather concentrate on success frameworks and animations. Speaker 1: So it allows you to be more precise about your choices.
Speaker 1: And this is also important in case your company provides some consulting services. Speaker 1: And this is the next part of my presentation. Speaker 1: So in case you are consulting your clients, your front end strategy becomes your product strategy because your front end skills is a product that you sell to your customers. Speaker 1: And it's no longer about enabling your own company, but also enabling your customers.
Speaker 1: This leads to the change in your why, in the assessment criteria that you have, because you have to have a look at the tech stack of your clients and at the needs of your clients. Speaker 1: And since the why, the underlying reasoning changes, it also changes your tech stack, your technology radar, your choices. Speaker 1: And inevitably, you have to face a tradeoff between your cash cows and state-of-the-art of future technologies.
Speaker 1: For example, if your clients use jQuery and you think you should sunset it, you have to be involved in some transition of this technology and your clients towards the future technologies or state-of-the-art technologies, which might be another source of projects, but maybe also a pain point for you. Speaker 1: Whereas as an internal strategy, you should align your tech stack within projects.
Speaker 1: Here, you should probably better diversify to be more stable in the market. Speaker 1: This is also the difference between the internal strategy for your company or the strategy if you were consult someone. Speaker 1: And there is, there will be a shift in soft skill requirements because you no longer need only brilliant developers, but also brilliant communicators.
Speaker 1: So you have to pay closer attention to trainings, to soft skill developers, development, um, communication of your colleagues, of your team. Speaker 1: To sum this all up, um, your front end strategy has to fit in into the whole strategic framework of your company. Speaker 1: You can reuse some existing documentation to align it better.
Speaker 1: You have to come up first with the, with the outer circle with this reasoning, how and why you're choosing technologies. What's important for your company? Speaker 1: Either through internal brainstorming or through the market research from your clients, um, their client, there's tech stack and needs. Speaker 1: And once you've done with this, you're able to choose technologies.
Speaker 1: You can structure them and document them your choices through the technology radar. Speaker 1: Uh, don't forget the people at the heart of your technology radar. Speaker 1: And once you're done with this, don't forget to reiterate, to reiterate once in a quarterly for the technology radar, for example, once in the year for, for the outer circle.
Speaker 1: And if needed, also the whole strategic framework. Speaker 1: That's it for today. Speaker 1: And by the way, there's a fun fact. This tips, um, can be also used for your personal front end strategy, but this is a topic for another talk. Speaker 1: Thank you for your attention and have a nice day.
Transcribed automatically; names checked against the speaker record. Select a time to jump there.
Article based on this talk
How do you choose frontend technologies without following the hype?
Maria Korneeva shows why a frontend strategy must start from business reasons, not from the latest framework list.
In short
Frontend trend lists are not a strategy. Maria Korneeva, Frontend Tech Lead at Aleri Solutions, argues that a frontend strategy has to fit into the company's existing strategic framework and start from clear assessment criteria (the "why"), and only then select technologies. She shows how to document those choices in a technology radar and how the picture changes when frontend skills are what a consulting company sells.
Key takeaways
Focus on business needs, not frameworks.
Segment your frontend competence.
Pair your team competence with career level.
Base your USP on hard facts.
Why trend articles were no help
When Korneeva was appointed frontend technology lead, her first assignment was a management summary on frontend strategy. Searching online turned up only a few links with tips, so she looked at the trend predictions published in December 2020. One site forecast progressive web apps, single page applications, motion design and TypeScript. Another listed the same four in a different order.
"So consistency is good, but I strongly sense the copy paste skills and that made me even more insecure how I'm supposed to choose." (1:21)
That experience became the starting point for the talk: if the forecasts cannot be trusted, a tech lead needs a method of her own.
Fit into the strategy you already have
Korneeva's first point is reassuring. Unless you are founding a startup, there is already a vision, a mission and a company strategy to align with.
"Usually, unless you start registering your startup, you wouldn't start from scratch." (2:31)
That framework brings constraints as well as help. If HR plans a pyramid with many associates and few seniors, the frontend plan must work within it or be negotiated with colleagues. Existing documents such as a business canvas already describe target customers and the unique selling proposition, and both can be reused. Korneeva also learned to make that USP provable. Her first draft described a highly professional, motivated, client-oriented team, and a sparring partner pushed back.
"However, my sparing partner said that I cannot prove this, so I'd better go with some fact based information." (3:54)
Industry knowledge backed by reference projects, end-to-end support backed by the team's skill set, partner contracts or certifications are claims that hold up.
A SWOT analysis for the frontend
Korneeva reused a SWOT analysis and shared the frontend-specific points she covered. It is hard to say where frontend stops and back end begins, especially with full stack developers. Competitors include freelancers, who often take on frontend work, as well as price-driven agencies and offshore companies. The opportunity is that frontend keeps getting more complex, so customers rely more on external expertise. The threats include the rise of low-code platforms and the lack of a widely recognised frontend certification.
"But for front end there is nothing, at least not that I know, which is really widely spread." (6:59)
She also notes that attention has moved towards IoT, blockchain and machine learning, which weakens frontend's position when negotiating budget. Add unclear scope (are static site generators or hybrid mobile apps frontend?), a new framework every week, and a reputation summed up by a dismissive German nickname for people who push pixels around. Above all, she stresses the human side: developer experience and training can make or break the best technology choice.
The core of Korneeva's method is to settle the reasons first. She points to a case study whose author began by listening to his own people.
"Talk to your developers, talk to your architects, ask them about their pain points, about the problems with the code base, the process of code review, all this stuff." (10:49)
Scrum masters and product owners add input on features, validation, releases and "big dreams if technology was no limit". That pool of ideas is then structured into clusters of requirements. In the case study, which resembles her own company's result, the clusters were customer and developer experience, technology as a product enabler, and cultural fit.
"And once you have this, once you know what's important for your company, then you can choose technologies and then you can overcome this framework hype." (10:29)
With criteria in place, she recommends a technology radar to document, assess and structure the stack: what to avoid, what to experiment with, what to focus on and what is already in use. Her company goes further, grouping competence into essentials, helpers, all-rounders, fancy sites and powerful apps. The essentials are responsive, accessible, cross-browser and cross-device apps. For bigger, more complex apps she points to Angular, while beautiful microsites call for CSS frameworks and animation skills.
When frontend is what you sell
For consulting companies, the logic shifts.
"So in case you are consulting your clients, your front end strategy becomes your product strategy because your front end skills is a product that you sell to your customers." (13:52)
The why now includes clients' tech stacks and needs, which changes the radar. There is a trade-off between cash cows and state-of-the-art technologies: if clients still run jQuery, moving them forward can be both a source of projects and a pain point. Where an internal strategy should align the tech stack across projects, a consultancy may do better to diversify. People requirements change too.
"And there is, there will be a shift in soft skill requirements because you no longer need only brilliant developers, but also brilliant communicators." (15:13)
Korneeva closes with a cadence: revisit the technology radar quarterly, the assessment criteria yearly and the whole strategic framework when needed, and keep people at the centre.
"Uh, don't forget the people at the heart of your technology radar." (16:20)
Watch the talk
Crafting Frontend Strategy, Maria Korneeva, 17 minutes: https://www.womentech.net/video/crafting-frontend-strategy
About the speaker
Maria Korneeva is Frontend Tech Lead at Aleri Solutions GmbH in Cologne, Germany, and describes herself as a problem solver currently focused on frontend and Angular in particular. She holds a master's degree in business informatics and a PhD in linguistics, and has lived and worked in Germany, Russia and Uzbekistan.
Questions this talk answers
Can annual web development trend articles guide a frontend strategy?
Where should a frontend strategy start?
How do you build criteria for choosing frontend technologies?
How does a frontend strategy differ for a consulting company?
How often should a frontend strategy be revisited?
Drafted with AI from the talk transcript. Editor review pending.
Frameworks and ideas mentioned
SWOT analysis
Business Model Canvas
Technology Radar
Unique selling proposition (USP)
Resources mentioned
Frontend strategy case study (linked on the speaker's slides)
Technology radar article (linked on the speaker's slides)
Speaker's articles for ng-conf
Cite this talk
Maria Korneeva. "Crafting Frontend Strategy." WomenTech Network, 2021. https://www.womentech.net/video/crafting-frontend-strategy