Overcoming the Business Front‑End Dilemma: Practical Strategies to Boost ROI and Technical Impact

Foreword

As a business‑oriented front‑end engineer, you may feel overworked, constantly firefighting, and still be told you lack business sense; the article aims to share insights and practical advice gathered from internal technical forums and senior experts.

Business Front‑End Dilemma

Busy Business Front‑End

Product releases are rushed, leaving little time for development.

Lack of early business knowledge makes it hard to judge requirements and propose better solutions.

High maintenance cost and endless small bugs consume daily work.

Legacy tech stacks and heavy custom logic slow down development and reuse.

Business Front‑End as “Resource”

Because front‑end work often follows visual designs, engineers can be treated as interchangeable code generators, losing the chance to influence product direction and ending up with messy code and low morale.

How to Break Through

Propose technical refactoring to modernise outdated systems.

Build a data‑centered integration platform to ease front‑back‑end collaboration.

Focus on performance optimisation for slow‑rendering pages.

…

The boss typically asks four soul‑searching questions: why do this (business & technical value), why now, why you, and what is the ROI.

Understanding the Business

Business vs. Requirements

Requirements are the product‑level expression of business needs; understanding the underlying business is essential to propose better solutions and avoid blind implementation.

Why Front‑End Should Learn Business

Knowing the business lets you spot opportunities that product owners miss.

It helps you see the bigger picture, identify pain points, and design solutions that truly add value.

It satisfies the personal drive to build impactful products.

Alibaba expects engineers to bridge technology and business, proactively supporting KPI achievement.

How to Learn Business

Read high‑rated books in the domain to build a knowledge framework.

Talk to business owners, senior ops or product colleagues to grasp history, vision, and expectations.

Follow weekly reports from partners to monitor progress toward goals.

Understand KPI targets, data metrics, and how your work contributes.

Ask concrete questions about the product, users, traffic layers, and revenue model.

Identify the pages you own and their business impact.

After each project, analyse post‑launch data to improve understanding, spot mismatches, and refine future work.

Technical Depth

Technical Knowledge vs. Ability

Knowledge (I KNOW): books such as “TypeScript from Intro to Mastery”, “React from Intro to Mastery”, “Webpack from Intro to Mastery”, etc.

Ability (I CAN): examples like refactoring a large system with TypeScript, delivering React Hooks training, optimizing Webpack builds, and other concrete achievements.

Building Technical Vision

Stay curious about industry trends; prototype promising new tech when relevant.

Research group‑wide and industry solutions to avoid reinventing wheels.

Systematic, Full‑Chain, Single‑Point Challenges

Systematic thinking: break complex problems into key factors and solve root causes.

Full‑chain perspective: consider the entire stack, not just front‑end.

Single‑point technical challenges: devise innovative solutions for specific tough problems.

Give You More Feel

Developing a strong business sense is difficult but essential; aligning technology with business goals creates breakthroughs and career growth. To deepen this experience, the Taobao tech team hosted three live streams covering A/B testing, live streaming, and edge computing.