# What should you define before building your first wearable? — SyntaForge

Canonical: https://syntaforge.com/en/blog/defining-first-wearable/
Language: en

> This is a text rendering of the same public webpage. Use the canonical URL for citation. Private inquiry records and administrator data are never included.

[← All articles](https://syntaforge.com/en/blog/) Product definition 2026-11-04 SyntaForge editorial

# What should you define before building your first wearable?

“Build a wristband” is a product format, but it is not yet a development brief. A better starting point is a person, a moment and a task the wearable needs to support.

In this article

[Start with a moment someone can describe](https://syntaforge.com/en/blog/defining-first-wearable/#journal-section-0) [Put the first-version decisions on one page](https://syntaforge.com/en/blog/defining-first-wearable/#journal-section-1) [Choose the information before choosing a screen](https://syntaforge.com/en/blog/defining-first-wearable/#journal-section-2) [Give the prototype a question to answer](https://syntaforge.com/en/blog/defining-first-wearable/#journal-section-3)
What should you define before building your first wearable?
Illustrative development scene

## Start with a moment someone can describe

Choose a specific moment: reviewing feedback after a training session, or receiving a task and confirming it on site. Turn broad goals such as wellbeing or productivity into an action a person can actually complete.

You do not need a complete feature list yet. Understand how the task happens today, where it becomes awkward and why a device worn on the body might help.

## Put the first-version decisions on one page

A first brief can cover five things: the user, the main task, the wearing and working environment, essential functions and functions deliberately left for later. Add how the device relates to a phone or an existing business system.

Every essential feature needs a reason. If removing it leaves the core task intact, it may belong in a later discussion. More features also introduce more questions to test.

## Choose the information before choosing a screen

Frequently reading tasks and checking values is a different interaction problem from receiving a simple reminder. Establish what must appear on the wrist, how long someone can look at it and whether their other hand is free. Then consider a small screen, no screen, buttons or another approach.

Connectivity, battery life and physical design need to be discussed together. Selecting them in isolation can leave difficult compromises for the assembly stage.

## Give the prototype a question to answer

The first prototype may have a narrow purpose: test wearing comfort, readability or an end-to-end data connection. Write down the question and what evidence would answer it.

Product definition is not a promise to resolve the entire future in one meeting. It is a shared decision about the next useful step. A one-page brief often makes that decision easier than a long, unprioritised feature list.

For your next discussion

Before the first discussion, write one sentence: who needs to do what, and at which moment?First published 2026-11-04 [Discuss a product](https://syntaforge.com/en/contact/)

## Keep reading.

[All articles](https://syntaforge.com/en/blog/)

[Why run a pilot batch after the prototype works?](https://syntaforge.com/en/blog/prototype-to-pilot/) Prototypes & production 2026-11-04

## [Why run a pilot batch after the prototype works?](https://syntaforge.com/en/blog/prototype-to-pilot/)

Separate “this unit works” from “the next batch can be built consistently”, and use a pilot build to check assembly, inspection and actual use.

[Read article](https://syntaforge.com/en/blog/prototype-to-pilot/)

[Starting from a wearable platform: what carries over?](https://syntaforge.com/en/blog/choosing-a-wearable-platform/) Hardware platforms 2026-11-04

## [Starting from a wearable platform: what carries over?](https://syntaforge.com/en/blog/choosing-a-wearable-platform/)

Assess wearing, interaction, connectivity and software separately. A familiar form is a starting point, not proof that a product fits the use case.

[Read article](https://syntaforge.com/en/blog/choosing-a-wearable-platform/)