← Work/2022 – 2024 · Product Designer

WOD.co

A workout platform built around the coach: a typed editor to write the class, a calendar that decides who sees it, and an iOS app where the athlete does it and logs the result.

In 60 seconds

Role
Product Designer
Timeline
2022 – 2024
Team
The WOD.co team, worked with up close in Taiwan; team size is not recorded

The challenge

Coaches ran live classes from spreadsheets, group chats and paper logs, because every tool in the category was built for athletes logging alone.

The insight

The coach was the unserved user. What reframed the product was a count, not a feature list: 47 context switches an hour, timed on the gym floor.

What I did

Shadowed six coaches through live classes, then designed the typed workout editor, the squad calendar, the athlete dashboard, the iOS app and the public site.

47 → 12

Coach context switches an hour in a live class

Research observation · Qualitative

60%

Less time spent programming workouts

Research observation · Qualitative

6

Coaches shadowed through live classes

Research observation · Qualitative

3

Tools benchmarked: Wodify, SugarWOD and BTWB

Benchmark · Qualitative

The switch counts and the programming time come from observation, not from instrumentation in the product. No usage, retention or revenue figures are recorded, so none are claimed.

How it beganBefore the first screen

The interview ended with a homework assignment: go and train.

The CEO asked why I wanted to work on CrossFit. I told him the truth: I had never done it. And anything I have not done yet pulls me in, because that is where I learn fastest.

01

A hidden gem, and a fog

To me the whole world was a hidden gem I had to discover. How do athletes actually practise? How is a workout written down? Where does a result go afterwards?

I could not answer any of it, and I had no way to see through the fog from a desk.

A CrossFit floor before class: plyo boxes, loaded barbells and a screen showing the workout
A floor before class. The workout is on the screen, the whiteboard and the coach's head, and nowhere else.

02

The assessment was the research

He did not ask me for a deck. He gave me an assessment, as part of the hiring: go to real CrossFit gyms, talk to the coaches and athletes, and find out which apps they use and how it really works. My first task was to leave the screen and stand in a room full of barbells.

A class seen from the floor, through the uprights of a rack
A class from the floor.
Someone lying on the floor of a gym with a leg up on a box, barbell beside them
How a class ends, for everyone.
Seven people posing after a class in front of a graffiti wall, flashing peace signs and shakas

03

It was painful. It was also the point.

You cannot ask a coach about a class you have never survived, so I did the classes too. CrossFit is nothing like a normal workout. It is much harder, and I felt every minute of it.

But it opened a door. I was standing in an area I had never been in, with questions I could finally ask in the right words.

04

One gym was not enough, so I went looking

I was in Turkey at the time, and one gym could not give me the whole picture, so I travelled: the Emirates, Egypt, then Taiwan. In every gym I watched the same three things: how athletes do the workouts, how they record them, and how coaches train them.

A gym floor with a living plant wall, kettlebells, ropes and rings
Another floor on the road. Different walls, the same question.

4 stops · 3 legs

Turkeyto Dubai

Leg 1 of 3

🇹🇷 Turkey
🇦🇪 Dubai
🇪🇬 Cairo
🇹🇼 Taiwan

05

Then I moved to Taiwan

By then I knew the product could not be designed from a distance, so I moved to Taiwan to work with the team up close, near the gyms and the people we were building for. It hurt at the beginning. It was also one of the most exciting stretches of the project, and everything on this page started on a gym floor.

Alhasan taking a selfie with a class at 4SC CrossFit, everyone smiling, holding cut-out signs
At 4SC CrossFit, after a session.

The problemWho it is for

A class runs on a clock, and the coach was running it from three places.

Twenty people are warming up while the coach checks the plan, answers a message and looks at what someone lifted last week. Each look is a different tool.

  1. In the room

    Twenty people warming up

  2. Spreadsheet

    Check the plan

  3. In the room

    Back to the class

  4. Group chat

    Answer a message

  5. In the room

    Back to the class

  6. Paper log

    What someone lifted last week

  7. In the room

    Back to the class

Six switches are drawn. Timed across six coaches, the real count was 47 an hour. The three places are what the observation recorded; the order here is an illustration, not a logged sequence.

The countWhat the observation measured

47 switches an hour, then 12.

Before

47

context switches an hour, timed across six coaches in live classes

Research observation· QualitativeTimed by observation

After

12

context switches an hour in a live class with WOD.co

Research observation· QualitativeTimed by observation

Time spent programming workouts

60% less

Research observation· QualitativeIn the coaches' own timing. Bars show the proportion only; no minutes are recorded.

These are research observations, not production metrics. Both counts come from timing coaches in live classes, not from instrumentation in the product. The number of classes behind the 12 is not recorded, and no usage, retention or revenue figures exist for this project, so none are claimed.

The coach was the unserved user, not the athlete logging alone.

Wodify, SugarWOD and BTWB were built for an athlete's solo logging session. So the product starts with the person standing in a loud gym, and the athlete's app is built from what that person writes.

The loopOne thing, passed along

What the coach writes is what the athlete logs against.

Five steps, three surfaces. The lettering the coach types, A and A1, is the lettering on the athlete's results sheet, and the result comes back to the coach as a number on a chart.

01

Write

Coach · web

A typed editor: sections, blocks and movements, with commands on a slash.

02

Plan

Coach · web

A calendar that decides what each athlete can see, and when.

03

Do

Athlete · iOS

Workout of the day: the plan, the movements, a way to ask how.

04

Log

Athlete · iOS

Results typed against the plan, with weights worked out and PRs flagged.

05

Review

Both

Volume, movement balance, streaks and records, back to the coach and the squad.

How we knewEvidence

What is recorded, what is not, and how far to trust it.

Interviews

Qualitative

6

Coaches shadowed through live classes, every context switch timed. The 47 an hour came from this and reframed the product.

Benchmark

Qualitative

3

Wodify, SugarWOD and BTWB. All three were built for the athlete's solo logging session; none was built for the coach running a room.

Confidence: Medium

Design judgement

Qualitative

60+

Captures read one by one: the web editor, calendar, athlete dashboard, iOS app and public site. The notes here describe only what is visible on them.

Research observation

Qualitative

47 → 12

Coach context switches an hour, with 60% less time programming workouts. Both come from timed observation, not from instrumentation in the product, so they are not production metrics.

Confidence: Medium

Usability test

Mixed

Flows were tested back in the gym, where the real constraints are noise, movement and time pressure. Participant numbers and timings are not published on this page.

Analytics

Quantitative

No figures for athletes, workouts posted, retention or revenue are recorded in the project files, so none are claimed here.

01 of 08

Writing the workout

The editor is a document. The title and date sit on one line, the workout is lettered sections, and the right-hand panel opens on whatever movement you point at, with its video, measurements, pattern, difficulty and tags. A warnings count at the foot says when something is off, and “Super clean workout” when it is not.

Create workout
Drag a section in from a list
Empty block and a movement's details
Turn a line into a section or block

Structure is typed, not built

Sections, blocks and movements are lines with letters (A, A1). The coach adds structure by typing and by pressing Tab, and the layout follows.

Sections come from lists

A Workouts lists panel holds ready-made sections, from WOD.co and from the coach's own box. “Drag and drop your desired section into the editor, and you're good to go.”

02 of 08

Planning the week

The calendar is where a programme becomes something a squad can see. A week is a row, a rest day has its own glyph, and an empty day offers four things: create a workout, add one from a list, mark a rest day, or paste one. The squad page above it carries members, views, completions and top scores.

Squad page and calendar
Calendar, coach side
Who sees the week, and when
Create from the calendar
Drag from lists onto a day
Select days, then act on them
Squad permissions

Create without leaving the grid

A new workout opens in a dialog over the calendar, with Publish at the top and an expand control for the full editor.

Messages stay one tap away

A docked Messages bar with an unread count lives at the foot of the screen, so a coach answers a question without losing their place.

03 of 08

The day, on a phone

The iOS app opens on the workout of the day: the week in a strip across the top, the workout as a card with its sections and movements, and the squad's activity under it. Tracking, Notes and Profile are a tap away, and a readiness status sits under the greeting.

Home
Readiness
Workout of the day
Full workout
Feed
Activity and charts
Notes

The card says enough to start

Sections, movements and “Tap to see full workout”, with Like, Save and Do Workout on the same card.

A personal log, next to the shared one

Notes puts the athlete's own workouts on a calendar, with an empty day shown as “No Workout” and a plus to add one.

04 of 08

Logging a result

Results are typed against the plan. A set written as a percentage shows the weight it means, a new PR is marked on the line it happened, and an EMOM asks for an interval and rounds on a number pad. Typed words are matched to the movement library, and the match can be kept as a shortcut.

Writing results
Results by set
Interval and rounds
A shortcut offered
Change movement
Match confirmed
Movement history
Records by rep count

A number pad for numbers

Interval and rounds are large figures with plus and minus, and an Insert button. No keyboard until the athlete needs words.

History shows where a number came from

A movement's page keeps its chart, its volume, its energy and its PRs by rep count, and flags that the 1RM is an estimate.

Underneath

Three surfaces, one vocabulary.

Section, block and movement mean the same on the web editor, in a calendar cell and on the phone's results sheet, down to the lettering. Colour is kept for meaning: black for the main action on the phone, coral for streaks, records and errors, green for gains, and one six-axis chart for movement balance that appears on the web dashboard, the phone's tracking tab and another athlete's profile.

DecisionsAnd the evidence behind them

What we saw, what we knew, what we chose, and what we gave up.

01

Let the coach write the workout the way they already write it

What we saw
A coach thinks in shorthand: EMOM8, AMRAP, 6-12-18-18, “find max load”. Spreadsheets and chat take that shorthand as it comes; most forms do not.
Evidence
Interviews· QualitativeSix coaches observed in live sessions, working from spreadsheets, group chats and paper logs.
Design judgement· QualitativeThe calendar cells in the captures are full of that vocabulary: time caps, rounds, sets written as rep schemes. The editor has to produce it, not replace it.
So we
A page you type into. Sections are lettered A, B; blocks A1, B1; movements are lines with small chips for what is measured (reps, weight, distance). Type “/” or right-click for commands and press Tab to format.
Not
A form with a field for every set, which asks a coach to fill in twelve boxes to say what one line says.
What happened
Time spent programming workouts fell by 60% in the coaches' own timing. The share that came from the editor, and the share from reusable sections, is not recorded separately.

02

Make visibility a rule on the calendar, not a button on every workout

What we saw
A coach plans a week at a time, but athletes do not need all of it at once, and some days are not decided yet.
Evidence
Prototype· QualitativeThe calendar control reads “Show workouts to athletes”: Weekly, Daily or Don't hide. Each week carries a green band, “Visible to athletes”, or an amber one, “Not visible to athletes”.
Design judgement· QualitativeThe same grid shows both states at once, so a coach can see what the squad can see without opening a preview.
So we
One rule for the squad's calendar, and a colour band over each week that says what it currently does.
Not
A publish button on every workout, which turns a week of programming into seven small decisions.
How we'd know
If coaches often override the rule by publishing a day early, the default is wrong. I would count overrides per squad in the first month.

03

Give a squad three roles, not a permissions matrix

What we saw
A box has a head coach, assistants who post workouts, and people who keep the community going. Giving everyone full control is easy and dangerous.
Evidence
Prototype· QualitativeSquad Permissions lists each person with one role: Admin, Post workouts only, or Monitor community. Adding someone is a search field and an Add button.
So we
Three named roles in one small dialog.
Not
Per-feature toggles for each member, which nobody maintains.
How we'd know
Do squads with three or more staff use the middle role? If nearly everyone is Admin, the roles are named wrong or the dialog is too easy to skip.

04

Let a typed word become the right movement

What we saw
Athletes write what they say out loud: “DU” for double unders, “DOB squat”. A strict picker makes them stop and search, in the middle of a set.
Evidence
Prototype· QualitativeTyping “DOB Squat” matches it to Squat, and a confirmation says “DOB Squat is now an alias to Squat”. After “DU”, a sheet asks whether to save it as a shortcut for Double Unders.
Design judgement· QualitativeThe movement's menu keeps the way out: Movement history, Change movement, Turn into Note, and a red Unlink Movement.
So we
Match as they type, offer to remember the shorthand, and keep every match undoable.
Not
A picker that rejects anything that is not already in the library.
How we'd know
Share of freehand movements that match on the first try, and how many are unlinked straight afterwards. A high unlink rate means the matching is guessing.

05

Work out the weight from the percentage

What we saw
Coaches programme in percentages (“5 reps at 50% of your one-rep max”). The athlete needs a number to put on the bar.
Evidence
Prototype· QualitativeThe results view lists each set as reps, percentage and the computed weight: 50% becomes 13 lbs, 60% becomes 15 lbs, and so on to 85%, with a PR flagged against the set it came from.
Design judgement· QualitativeMovement history shows an Estimated 1RM with a tooltip, “estimated based on your past performance”, and an Adjust 1RM control beside it.
So we
Show the percentage the coach wrote and the weight it means, and let the athlete correct the estimate.
Not
Printing percentages and leaving the arithmetic to the athlete, between sets.
How we'd know
Where athletes adjust the estimate, it was wrong. I would track how often they do, and whether the adjusted number sticks.

06

Make being hurt a one-tap status

What we saw
A coach cannot adjust a session for someone they do not know is injured, and telling them is awkward and easy to skip.
Evidence
Prototype· QualitativeA Readiness sheet offers Active, On a Break, Sick and Injured, each with a short line. The choice shows on the athlete's profile, and the weekly tracking chart marks injury and rest days in place of a bar.
So we
Four statuses, one tap, visible where the coach already looks.
Not
A free-text note, which gets written once and never updated.
How we'd know
Do athletes change their status back when they recover? A status that stays on Injured for a month is the sign it has become a chore.

TestingRun, and passed

The test, and how it came out.

The flows were taken back into the environment they were designed for: standing, moving, in noise, against a clock. Each task below was run on the real screens, against a pass bar written before anyone was asked.

You are mid-class and the coach says “three rounds, back squat at seventy-five percent.” Open today's workout and tell me what goes on your bar.

Time to the number, and whether they trust it

5 of 5 within 20 seconds

Passed

“You wrote DU in your log. Make sure it counts as double unders next time.”

Finds the shortcut sheet, accepts it, then undoes it

4 of 5 without help

Passed

“You hurt your shoulder this morning. Let your coach know without messaging them.”

Finds Readiness, picks Injured

5 of 5 within 15 seconds

Passed

Coach side: “Next week is written. Make sure athletes only see Monday.”

Finds Show workouts to athletes and sets Daily

4 of 5 first try

Passed

Coach side: “Add a movement to the second block without leaving the keyboard.”

Uses “/” or Tab, and any mouse trips

4 of 5 with no more than one mouse trip

Passed

Every task met its pass bar. Participant details and timings are not published on this page.

The trade-off

I chose a typed, document-style editor over a form with a field for every set. The cost is that a free line can be wrong in ways a form cannot, so the editor needs a warnings count and a movement match to catch it. I kept AI out of the live class entirely, because a coach owns what the room does next.

What it did

Coach context switches dropped from 47 to 12 an hour in a live class, and the time spent programming workouts fell by 60%. Both are research observations, timed in live classes rather than measured in the product. Athlete numbers, retention and revenue are not recorded, so I do not state them.

More detailsWhat did not fit above

My partProduct Designer, 2022 – 2024

What I did.

Tools and methods

Figma · Contextual inquiry · Competitive analysis · Prototyping · iOS · Web app design

  • Ran the shadowing study with six coaches and quantified the context-switching cost
  • Benchmarked Wodify, SugarWOD and BTWB to locate the unserved job
  • Designed the typed workout editor: sections, blocks, movements, slash commands, drag from lists and the states around them
  • Designed the squad calendar: visibility rules, rest days, create from a day and squad roles
  • Designed the athlete dashboard and the iOS app, from onboarding and the workout of the day to logging results, 1RM maths, movement matching, tracking and sharing
  • Designed the public site and its mobile version
© 2026 Alhasan HosniHome