← View all Templates

Technical specs.

How two Lyft engineers structure technical specs.

Created by Workflowy.

You must be logged in to copy a template

About this template

The technical spec serves as a bedrock document for specifying exactly what needs to be done, what the goals of the project are, and how you plan to measure the performance.

Clearly written technical specs help you to avoid some of the most common issues when dealing with the chaos of managing a project or feature to completion. Issues such as feature bloat, building something using outdated specs, building upon deprecated services, etc.

One key piece of advice the template authors provide is to make sure it's clear what the purpose of the technical spec is. "A tech spec without a purpose? It’s a waste of time." they note.

So take a moment to consider the following before you dive into writing:

  • What is the purpose of the document (to inform, to convince, to explore)
  • What level of detail you should go into, or not go into (high-level , low-level)
  • Who will be reading the tech spec (other engineers, stakeholders, QA)

This template is adapted from a post from the Lyft engineering blog. The original article can be found at the Lyft engineering blog.

Related templates

View all Templates

As simple as paper. Absurdly powerful.

Radical clarity and focus are only a signup away

Sign up What is Workflowy?
Product
Resources
Use Cases
About
Follow us