Engineering leadership tips
Posts argued design systems and early engineering involvement speed delivery by standardising components and running discovery spikes before handoff, which reduces one‑offs and rework. The advice was framed as ways to make cross‑team decisions less risky and more reusable. (x.com 1) (x.com 2)
Engineering teams are converging on a simple delivery rule: reuse more of the interface, and involve engineers before design handoff. (nngroup.com) A design system is a shared library of components, patterns, and rules that teams can apply across products instead of rebuilding screens one by one. A 2024 Aalto University thesis on Agile teams found that design systems improved cross-team communication by giving teams shared guidelines, documentation, and clearer roles. (aaltodoc.aalto.fi) Early engineering involvement usually happens through discovery work before implementation starts. Nielsen Norman Group said discovery is meant to learn about a problem before developing solutions, and warned that teams that rush or skip it work from “short-sighted or incorrect information.” (nngroup.com) In Agile practice, one common format is a spike: a short research task used to test feasibility, architecture, or estimates before committing to full delivery. Scaled Agile Framework said spikes exist to reduce technical risk, better understand requirements, and improve the reliability of story estimates. (framework.scaledagile.com) That advice has spread as product teams try to avoid the old “throw it over the wall” handoff, where design finishes first and engineering discovers constraints later. Atlassian said product discovery should not happen “in a vacuum” and should stay connected to delivery status and engineering reality. (atlassian.com) The tradeoff is that both habits cost time up front. The Aalto study said design-system adoption requires alignment across teams, structured communication, and ongoing maintenance, even when the long-term goal is fewer one-off decisions. (aaltodoc.aalto.fi) Discovery work also has to stay narrow, or it turns into open-ended research that delays shipping. Nielsen Norman Group recommended scaling discovery to targeted questions and writing down the implications and next steps in a one-page recap. (nngroup.com) The through line is not speed from working faster; it is speed from making fewer custom choices and catching bad assumptions earlier. Teams that standardize common parts and test unknowns before handoff are trying to make each next decision smaller than the last. (framework.scaledagile.com)
