0:0017:06

Crafting Frontend Strategy

Maria Korneeva 17:06 2021

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

Watch on YouTube

In short

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!

Topics

Related talks

Browse the library