Unlocking the engineering jungle for designers

I gave a talk at DesignWich School called "Designers to Know Engineering World." The goal was simple: help designers understand how engineering teams work so they can collaborate better.

Here is the quick version.

1. Business Analyst (BA)

The BA translates business needs into requirements the engineering team can act on. They sit between what users want and what the business needs. When a BA is good, requirements are clear. When they are missing, engineers are guessing.

2. Data Analyst

Data analysts turn raw numbers into insights. They answer questions like "is this feature actually being used?" and "where are users dropping off?" Designers who work closely with data analysts make better design decisions.

3. Product Manager / Product Lead

The PM owns the what and why. They prioritize features, define the roadmap, and make trade-off decisions. They are not your boss -- they are your partner. The best designer-PM relationships I have seen are built on mutual respect and honest disagreement.

4. Scrum

Scrum is a framework for building things in short cycles called sprints (usually two weeks). Daily standups, sprint planning, retrospectives. It is not perfect, but it gives teams a rhythm. Understanding Scrum helps designers know when and how to provide input so it actually gets implemented.

Why This Matters

The best products come from designers and engineers who understand each other's world. You do not need to write code. But understanding how engineering teams think, plan, and deliver will make you a more effective collaborator and a better designer.