Ward Rounding(0 more)
Ward 7
Nalintra Srisakorn07:04–08:01 · 57m
Since 2018, Mutrack has had one mission: to help our customers become better decision-makers. We work with hospitals in Thailand, on the way to a
Precision Society.
What we do
We help hospitals run better, and more profitably.
Step by step, we make the work behind the care digital: less cost, less waiting, more done.
Dispatcher Gets every job to the right person, with no one chasing it. Wi-FiBLE
Linen Counts every piece of linen, without counting. RFID
People Shows how work flows through people. BLE
Things Finds any piece of equipment in minutes. BLE
Admin Runs the infrastructure underneath them all.
One platform, built on our own hardware and software, from the first idea to installation and support, all knowing what, who, where and when in real time. Just enough technology to solve each problem well, at a price that makes sense.
Results
Technology can change a hospital in two ways. The first helps it earn more: the systems at the heart of how medical care is given. The second changes how the work behind that care is run: patients moved, linen washed, equipment found, people where they are needed. That is the kind Mutrack brings. It brings costs down, and keeps them down, by removing waste from everyday work, continuously.
2 million+ jobs sent to the right person by Dispatcher
6 hospitals public and private, run on Mutrack
30,000+ staff presences by area and counting, every minute
More than 80 million linen scans in, out and off to the laundry
10 million+ minutes saved for staff and patients alike
30% shorter service, with automatic assignment
A 7× smaller budget for buying new linen
Over 1,000 people log in every day to get the work done
These figures are other hospitals’. Your own hospital has its own: how many porters move its patients, how much linen goes to the laundry, how many devices and people there are to keep track of. Tell us about them, and we’ll work out with you what Mutrack would cost and what it would give back.
Our experiments
Some of what we build starts as an experiment, often with our interns, before it is a product. These are the ones far enough along to show you.
I’m Mu I understand your operation. Talks
We talk about what we learn. Each talk is built and given on this site, so what plays below is the talk itself, as the room saw it. Open it, and go through it at your own pace.
KMUTNB, Bangkok · 3 August 2026 Writing
We write to think deeply, share stories, challenge ourselves, encourage others, stay optimistic, and learn from mistakes.
Customization Is a Trap: Why We Choose Flexibility Instead Everyone wants software that feels tailor-made. A tweak here, a custom report there—it seems harmless. But over time, these one-off changes quietly erode product stability, increase support debt, and slow down innovation. This article explores the hidden costs of software customization and makes the case for building flexible systems instead—systems that empower users without compromising structure, speed, or long-term scalability. If you’re building platforms that are meant to last, this is a call to choose clarity over compromise and flexibility over fragmentation. 21 August 2025 Opinionated Product Development: Build with Vision, Love, and Care Great products don’t come from saying yes to everything. They come from strong opinions, clear beliefs, and the courage to build for someone—not everyone. This piece explores why being opinionated is not arrogance, but leadership—and how vision, love, and care are the most radical product features of all. If you’re building something meaningful, this is your invitation to do it on your own terms. 14 August 2025 Optimizing for Sharable Stories Most people chase money, titles, and status—things that look like success but feel empty over time. This is a story about choosing meaning instead. About staying small, trusting young people, walking away from big deals—and remembering the moments that made it all worth it. 7 August 2025About us
Bringing digitalization to hospitals, together.
Mutrack is part of the movement toward a Precision Society—a future where healthcare is smarter, more efficient, and free of unnecessary waste.
Our storyGet to know us better—our why, mission, and the journey we’re heading. We believe in small steps that lead to big changes. Every hospital we work with teaches us something new, and we’re grateful to play a part in making healthcare more efficient, transparent, and data-driven.
Every piece of linen, counted without counting.
Linen counts every piece of linen in the hospital as it moves: from the Main Store to the wards, out to the laundry, and back. A whole cart is counted in seconds, so the hospital finally knows what it has, and where.
Nobody can say where they went: lost on the wards, or lost at the laundry. The hospital buys more anyway.
Linen goes missing in two ways, and both stay out of sight.
Internal loss
Out to a ward or a clinic, and never back to the store.
External loss
Out to the laundry, and never back. It left weighed by the kilo, so nobody can prove how many went.
Nobody counts linen piece by piece: used linen leaves weighed by the kilo, and infectious linen can’t be opened to count at all.
It isn’t too little linen. It’s linen nobody can see.
Buying more makes the cycle bigger, not clearer. What helps is seeing the linen you already have.
Every piece of linen carries a small RFID tag, sewn in once and good for 200 washes. A handheld reader counts a whole cart in seconds, sorted by type, without anyone touching a piece. So linen is counted wherever it moves: out of the Main Store, into each ward, through the dirty room, out to the laundry and back.
Linen follows the cycle the hospital already runs. Each place counts what comes in and what goes out, with the hardware that suits it.
Main Store
Where clean linen is kept. An RFID chamber reads up to 300 pieces at once, as a whole cart goes in or out.
Substore
A ward or a clinic, with its own par level. A handheld reader paired with a phone checks linen in and out through the day.
Dirty Room
Where used linen waits for the laundry. It is counted by type before it leaves, infectious linen too, without opening a bag.
Laundry
In-house or outside, one or several. What goes out is counted by SKU, and what comes back is checked against it, piece by piece.
Counting is the start. These help the same team keep every ward stocked, and every piece accounted for.
01
RFID tags
02
Handheld reader
03
Par values for every location
Set what each ward should hold, type by type, and see at a glance how close it is.
04
Replenishment helper
Suggests what to send each location, and how many, from what it holds against its par.
05
Delivery through Dispatcher
The suggestion becomes a delivery job, and the nearest free messenger brings the linen.
06
Wash count and history
Every piece’s washes, age and last place, with its whole timeline in the app.
07
Not seen report
Linen nobody has scanned for a set time, with where it was last seen. Mark it lost in one go.
08
Lost and found
Mark linen as lost, and Linen spots it the moment it is scanned again.
09
Claim and obsolete
Worn-out pieces are retired; those a laundry lost or damaged are claimed back.
10
Rewash, kept apart
Linen sent back to be washed again is reported on its own, apart from the day’s washing.
11
Safety stock
Spare linen kept aside, pulled when needed, with a reminder to restock.
12
Every report you need
Clean and dirty linen, rewash, lost, replenishment, expense, obsolete and claim.
Follow one cart of used linen through a day: counted by type as it leaves the Dirty Room, kept in sight while it is at the laundry, and paid for only as it comes back.
0
Linen4 types
338 pieces sent to Clearwater Laundry
Scan, then send
A cart of used linen is counted by type in seconds, then checked out to the laundry.
Clearwater LaundryOverdue after 24 hours
Morning pickup2,949
3 of 24 hoursLinen47 types
At the laundry
Every piece sent is known by type, so what is out, and for how long, stays in sight.
Clean Linen ReportClearwater Laundry · Today, both deliveriesRun report
| SKU | Linen | Pieces | Price (THB) | Total (THB) |
|---|---|---|---|---|
| BED0001 | Bed sheet white single | 507 | 12 | 6,084 |
| BED0002 | Bed sheet white double | 13 | 12 | 156 |
| BED0003 | Bed sheet blue single | 415 | 12 | 4,980 |
| BED0004 | Bed sheet blue double | 18 | 12 | 216 |
| BED0005 | Fitted sheet white single | 329 | 12 | 3,948 |
| BED0006 | Fitted sheet white double | 16 | 12 | 192 |
| BED0008 | Draw sheet white | 844 | 8 | 6,752 |
| BED0009 | Draw sheet blue | 37 | 8 | 296 |
| BED0010 | Draw sheet pink | 88 | 8 | 704 |
| BED0011 | Pillowcase white | 627 | 5 | 3,135 |
| BED0012 | Pillowcase blue | 30 | 5 | 150 |
| BED0013 | Pillowcase pink | 63 | 5 | 315 |
| BED0014 | Pillowcase beige | 68 | 5 | 340 |
| BED0015 | Blanket beige XL | 8 | 15 | 120 |
| BED0016 | Blanket beige L | 147 | 15 | 2,205 |
| BED0017 | Blanket blue L | 8 | 15 | 120 |
| BED0018 | Blanket white L | 20 | 15 | 300 |
| BED0019 | Bedspread beige | 3 | 15 | 45 |
| BED0020 | Bedspread blue | 3 | 15 | 45 |
| BED0022 | Mattress cover double | 5 | 12 | 60 |
| BAT0004 | Hand towel white | 146 | 4 | 584 |
| PSU0001 | Kimono S | 35 | 10 | 350 |
| PSU0002 | Kimono M | 83 | 10 | 830 |
| PSU0003 | Kimono L | 69 | 10 | 690 |
| PSU0004 | Kimono XL | 32 | 10 | 320 |
| PSU0006 | Patient shirt female M | 96 | 8 | 768 |
| PSU0007 | Patient shirt female L | 127 | 8 | 1,016 |
| PSU0008 | Patient shirt female XL | 59 | 8 | 472 |
| PSU0010 | Patient shirt male M | 144 | 8 | 1,152 |
| PSU0011 | Patient shirt male L | 133 | 8 | 1,064 |
| PSU0012 | Patient shirt male XL | 66 | 8 | 528 |
| PSU0014 | Patient pants female M | 136 | 8 | 1,088 |
| PSU0015 | Patient pants female L | 155 | 8 | 1,240 |
| PSU0016 | Patient pants female XL | 63 | 8 | 504 |
| PSU0018 | Patient pants male M | 140 | 8 | 1,120 |
| PSU0019 | Patient pants male L | 134 | 8 | 1,072 |
| PSU0020 | Patient pants male XL | 65 | 8 | 520 |
| PSU0021 | Patient gown S | 16 | 10 | 160 |
| PSU0022 | Patient gown M | 46 | 10 | 460 |
| PSU0023 | Patient gown L | 46 | 10 | 460 |
| PSU0024 | Patient gown XL | 19 | 10 | 190 |
| PSU0025 | Maternity gown M | 22 | 10 | 220 |
| PSU0026 | Maternity gown L | 21 | 10 | 210 |
| PSU0027 | Maternity gown XL | 8 | 10 | 80 |
| PSU0028 | Child suit S | 9 | 8 | 72 |
| PSU0029 | Child suit M | 18 | 8 | 144 |
| PSU0030 | Child suit L | 23 | 8 | 184 |
Total · 5,160 pieces45,661 THB
Pay for what came back
Clean linen is counted in by SKU, and the laundry is paid per piece, for exactly what it returned.
When a ward runs low, Linen sends the delivery to Dispatcher, and the nearest free messenger brings the linen.

Linen
Counts every piece, and asks for more when a ward runs low.

Sends the nearest free messenger with the delivery.

The tags, readers and places underneath.
Every scan leaves a record of what moved, where, and when. Managers see the whole cycle as it happens, and plan next year’s purchase from what really happened in the last.
Linen runs every day, scan after scan. This is what it has added up to so far.

The last three come from a 580-bed private hospital, measured in 2021. With every piece in sight, it also held 10% less linen than before, not more.
The tags
Radio-frequency identification: a small tag a reader can identify by radio, without seeing or touching it. We use washable UHF tags made for industrial laundries. They need no battery, and suit things counted in large numbers, like linen.
It is guaranteed for 200 washes, and often lasts longer. Most linen wears out before its tag does.
Up to about three metres in theory; in practice, half a metre gives fast, accurate counts. Metal close to where you scan gets in the way.
Stand close to the linen and move the reader around it for 20 to 30 seconds, then scan again to check the numbers match.
Your own team can. If you use an outside laundry, the laundry can do it for you, depending on your agreement with them.
Getting started
No. Start small: choose the types of linen to tag and the departments they go to, then add pieces and departments as you need.
No. Linen works on its own: the phones need only a SIM card to reach our cloud software. You prepare the SIM cards, your starting data and the linen, and we install the rest.
With a visit. We see how your linen moves today and the spaces it moves through, then recommend how to use Linen to get the most from it.
If this sounds like your hospital, we’d like to hear how your linen moves today.
The rest of the system
A month’s roster, planned in minutes, and argued with.
Every month, someone sits down to decide who works when. For a team of thirty porters, that takes three to five days. Every shift needs its supervisor, its seniors and its porters; people have asked for days off; everyone needs rest between shifts and a day off in every week; and the same few should not always get the nights. A person can hold any two of these in mind at once. Roster holds them all, and plans the month in ten minutes at most.
Roster began with our interns. In 2024, Class 24 took a year of porter jobs, predicted the work at each hub hour by hour, and grouped the porters by how they worked. Class 25 came to build on it, and in their first week we decided together to turn to rostering. They wrote Roster’s first engine; I have built the rest on what they started, and their ideas still shape it.


Class 25 · 2025 The first engine. In their first week we turned to rostering together. They wrote the engine that searches for the month that fits. 
Mutrack Built in full. The web application, the Evaluator, the modes, and a real team’s month: three to five days down to ten minutes.
A manager describes her team once: who is on it, the shifts, how many of each role every shift needs on each day of the week, and the rules. Then each month she asks for a plan. Roster first looks over what she has given it, then searches: a genetic algorithm breeds generation after generation of possible rosters and keeps the best, telling her as it goes what it is doing.
1 Templates
Logistics TeamSlot8 shifts
| Order | Name | Start | End | Duration | Headcounts |
|---|---|---|---|---|---|
| 1 | Day Long | 07:00 | 19:00 | 12 hours | 3 MondaySupervisor: 1Senior: 0Agent: 2 3 TuesdaySupervisor: 1Senior: 0Agent: 2 3 WednesdaySupervisor: 1Senior: 0Agent: 2 3 ThursdaySupervisor: 1Senior: 0Agent: 2 3 FridaySupervisor: 1Senior: 0Agent: 2 3 SaturdaySupervisor: 1Senior: 0Agent: 2 3 SundaySupervisor: 1Senior: 0Agent: 2 |
| 2 | Day Standard | 08:00 | 18:00 | 10 hours | 3 MondaySupervisor: 0Senior: 1Agent: 2 3 TuesdaySupervisor: 0Senior: 1Agent: 2 3 WednesdaySupervisor: 0Senior: 1Agent: 2 3 ThursdaySupervisor: 0Senior: 1Agent: 2 3 FridaySupervisor: 0Senior: 1Agent: 2 3 SaturdaySupervisor: 0Senior: 1Agent: 2 3 SundaySupervisor: 0Senior: 1Agent: 2 |
| 3 | Day Short | 09:00 | 17:00 | 8 hours | 3 MondaySupervisor: 0Senior: 0Agent: 3 3 TuesdaySupervisor: 0Senior: 0Agent: 3 3 WednesdaySupervisor: 0Senior: 0Agent: 3 3 ThursdaySupervisor: 0Senior: 0Agent: 3 3 FridaySupervisor: 0Senior: 0Agent: 3 3 SaturdaySupervisor: 0Senior: 0Agent: 3 3 SundaySupervisor: 0Senior: 0Agent: 3 |
| 4 | Day Extended | 09:00 | 19:00 | 10 hours | 2 MondaySupervisor: 0Senior: 1Agent: 1 2 TuesdaySupervisor: 0Senior: 1Agent: 1 2 WednesdaySupervisor: 0Senior: 1Agent: 1 2 ThursdaySupervisor: 0Senior: 1Agent: 1 2 FridaySupervisor: 0Senior: 1Agent: 1 2 SaturdaySupervisor: 0Senior: 1Agent: 1 2 SundaySupervisor: 0Senior: 1Agent: 1 |
| 5 | Mid Morning | 10:00 | 20:00 | 10 hours | 2 MondaySupervisor: 0Senior: 0Agent: 2 2 TuesdaySupervisor: 0Senior: 0Agent: 2 2 WednesdaySupervisor: 0Senior: 0Agent: 2 2 ThursdaySupervisor: 0Senior: 0Agent: 2 2 FridaySupervisor: 0Senior: 0Agent: 2 2 SaturdaySupervisor: 0Senior: 0Agent: 2 2 SundaySupervisor: 0Senior: 0Agent: 2 |
| 6 | Mid Day | 10:00 | 18:00 | 8 hours | 3 MondaySupervisor: 0Senior: 1Agent: 2 3 TuesdaySupervisor: 0Senior: 1Agent: 2 3 WednesdaySupervisor: 0Senior: 1Agent: 2 3 ThursdaySupervisor: 0Senior: 1Agent: 2 3 FridaySupervisor: 0Senior: 1Agent: 2 3 SaturdaySupervisor: 0Senior: 1Agent: 2 3 SundaySupervisor: 0Senior: 1Agent: 2 |
| 7 | Afternoon | 11:00 | 22:00 | 11 hours | 2 MondaySupervisor: 1Senior: 0Agent: 1 2 TuesdaySupervisor: 1Senior: 0Agent: 1 2 WednesdaySupervisor: 1Senior: 0Agent: 1 2 ThursdaySupervisor: 1Senior: 0Agent: 1 2 FridaySupervisor: 1Senior: 0Agent: 1 2 SaturdaySupervisor: 1Senior: 0Agent: 1 2 SundaySupervisor: 1Senior: 0Agent: 1 |
| 8 | Night | 19:00 | 07:00 | 12 hours + 1 day | 2 MondaySupervisor: 0Senior: 1Agent: 1 2 TuesdaySupervisor: 0Senior: 1Agent: 1 2 WednesdaySupervisor: 0Senior: 1Agent: 1 2 ThursdaySupervisor: 0Senior: 1Agent: 1 2 FridaySupervisor: 0Senior: 1Agent: 1 2 SaturdaySupervisor: 0Senior: 1Agent: 1 2 SundaySupervisor: 0Senior: 1Agent: 1 |
1 Plans2 Plans
| Schedule Name | Template | Month | Optimization Mode | Status | |
|---|---|---|---|---|---|
| December 2026 | Logistics Team | December 2026 | Coverage | DraftPublished | |
| November 2026 | Logistics Team | November 2026 | Coverage | Published |
Create Schedule
Optional — if no budget is set for this month yet, leave it blank
Create Schedule
30 members
| Name | Gender | Role | Normal Hours | Overtime Hours | Total Hours | Workday | Days off |
|---|---|---|---|---|---|---|---|
Ananya PongpanitchLogistics Supervisor | Female | Supervisor | 0 | 0 | 0 | 0 | 31 |
Anucha BoonmeePorter | Male | Agent | 0 | 0 | 0 | 0 | 31 |
Chaiwat InthongSenior Porter | Male | Senior | 0 | 0 | 0 | 0 | 31 |
Jiraporn WongsaSenior Porter | Female | Senior | 0 | 0 | 0 | 0 | 31 |
Kittipong ChaiyasitPorter | Male | Agent | 0 | 0 | 0 | 0 | 31 |
Pongpisut PatamadechaPorter | Male | Agent | 0 | 0 | 0 | 0 | 31 |
Siriporn ThongdeePorter | Female | Agent | 0 | 0 | 0 | 0 | 31 |
Tachapol UdomaekPorter | Male | Agent | 0 | 0 | 0 | 0 | 31 |
Tanagorn RattanapanPorter | Male | Agent | 0 | 0 | 0 | 0 | 31 |
Traitod PrachayutMessenger | Male | Agent | 0 | 0 | 0 | 0 | 31 |
Wanpen SukjaiPorter | Female | Agent | 0 | 0 | 0 | 0 | 31 |
Wiroj SaengthongSenior Porter | Male | Senior | 0 | 0 | 0 | 0 | 31 |
Apichat MoonsriPorter | Male | Agent | 0 | 0 | 0 | 0 | 31 |
Duangjai PhetcharaPorter | Female | Agent | 0 | 0 | 0 | 0 | 31 |
Kanokwan PetchrungPorter | Female | Agent | 0 | 0 | 0 | 0 | 31 |
Kriangkrai SomboonPorter | Male | Agent | 0 | 0 | 0 | 0 | 31 |
| NNantana SrisukShift Supervisor | Female | Supervisor | 0 | 0 | 0 | 0 | 31 |
Naruemon ChaisriPorter | Female | Agent | 0 | 0 | 0 | 0 | 31 |
Nattapon SrichaiPorter | Male | Agent | 0 | 0 | 0 | 0 | 31 |
Phichit BoonchuPorter | Male | Agent | 0 | 0 | 0 | 0 | 31 |
Pornthip SaengdaoPorter | Female | Agent | 0 | 0 | 0 | 0 | 31 |
| PPrasit WongwanShift Supervisor | Male | Supervisor | 0 | 0 | 0 | 0 | 31 |
Ratchanee BoonrodSenior Porter | Female | Senior | 0 | 0 | 0 | 0 | 31 |
Sakda PhonsriSenior Porter | Male | Senior | 0 | 0 | 0 | 0 | 31 |
Somsak ThongmakPorter | Male | Agent | 0 | 0 | 0 | 0 | 31 |
Sunisa WongprasertPorter | Female | Agent | 0 | 0 | 0 | 0 | 31 |
Surasak InkaewPorter | Male | Agent | 0 | 0 | 0 | 0 | 31 |
Thawatchai KaewkhamPorter | Male | Agent | 0 | 0 | 0 | 0 | 31 |
Weerapong SaelimSenior Porter | Male | Senior | 0 | 0 | 0 | 0 | 31 |
Yupin NakprasertPorter | Female | Agent | 0 | 0 | 0 | 0 | 31 |
| Name | Gender | Role | Normal Hours | Overtime Hours | Total Hours | Workday | Days off |
|---|---|---|---|---|---|---|---|
Ananya PongpanitchLogistics Supervisor | Female | Supervisor | 240 | 0 | 240 | 20 | 11 |
Anucha BoonmeePorter | Male | Agent | 240 | 0 | 240 | 20 | 11 |
Chaiwat InthongSenior Porter | Male | Senior | 252 | 0 | 252 | 21 | 10 |
Jiraporn WongsaSenior Porter | Female | Senior | 252 | 0 | 252 | 21 | 10 |
Kittipong ChaiyasitPorter | Male | Agent | 240 | 0 | 240 | 20 | 11 |
Pongpisut PatamadechaPorter | Male | Agent | 264 | 0 | 264 | 22 | 9 |
Siriporn ThongdeePorter | Female | Agent | 252 | 0 | 252 | 21 | 10 |
Tachapol UdomaekPorter | Male | Agent | 240 | 0 | 240 | 20 | 11 |
Tanagorn RattanapanPorter | Male | Agent | 264 | 0 | 264 | 22 | 9 |
Traitod PrachayutMessenger | Male | Agent | 252 | 0 | 252 | 21 | 10 |
Wanpen SukjaiPorter | Female | Agent | 240 | 0 | 240 | 20 | 11 |
Wiroj SaengthongSenior Porter | Male | Senior | 240 | 0 | 240 | 20 | 11 |
Apichat MoonsriPorter | Male | Agent | 240 | 0 | 240 | 20 | 11 |
Duangjai PhetcharaPorter | Female | Agent | 264 | 0 | 264 | 22 | 9 |
Kanokwan PetchrungPorter | Female | Agent | 252 | 0 | 252 | 21 | 10 |
Kriangkrai SomboonPorter | Male | Agent | 240 | 0 | 240 | 20 | 11 |
| NNantana SrisukShift Supervisor | Female | Supervisor | 264 | 0 | 264 | 22 | 9 |
Naruemon ChaisriPorter | Female | Agent | 240 | 0 | 240 | 20 | 11 |
Nattapon SrichaiPorter | Male | Agent | 252 | 0 | 252 | 21 | 10 |
Phichit BoonchuPorter | Male | Agent | 240 | 0 | 240 | 20 | 11 |
Pornthip SaengdaoPorter | Female | Agent | 240 | 0 | 240 | 20 | 11 |
| PPrasit WongwanShift Supervisor | Male | Supervisor | 240 | 0 | 240 | 20 | 11 |
Ratchanee BoonrodSenior Porter | Female | Senior | 240 | 0 | 240 | 20 | 11 |
Sakda PhonsriSenior Porter | Male | Senior | 228 | 0 | 228 | 19 | 12 |
Somsak ThongmakPorter | Male | Agent | 252 | 0 | 252 | 21 | 10 |
Sunisa WongprasertPorter | Female | Agent | 240 | 0 | 240 | 20 | 11 |
Surasak InkaewPorter | Male | Agent | 252 | 0 | 252 | 21 | 10 |
Thawatchai KaewkhamPorter | Male | Agent | 240 | 0 | 240 | 20 | 11 |
Weerapong SaelimSenior Porter | Male | Senior | 252 | 0 | 252 | 21 | 10 |
Yupin NakprasertPorter | Female | Agent | 252 | 0 | 252 | 21 | 10 |
| Name | Gender | Role | Normal Hours | Overtime Hours | Total Hours | Workday | Days off |
|---|---|---|---|---|---|---|---|
Ananya PongpanitchLogistics Supervisor | Female | Supervisor | 240 | 0 | 240 | 20 | 11 |
Anucha BoonmeePorter | Male | Agent | 240 | 0 | 240 | 20 | 11 |
Chaiwat InthongSenior Porter | Male | Senior | 264 | 0 | 264 | 22 | 9 |
Jiraporn WongsaSenior Porter | Female | Senior | 252 | 0 | 252 | 21 | 10 |
Kittipong ChaiyasitPorter | Male | Agent | 240 | 0 | 240 | 20 | 11 |
Pongpisut PatamadechaPorter | Male | Agent | 264 | 0 | 264 | 22 | 9 |
Siriporn ThongdeePorter | Female | Agent | 252 | 0 | 252 | 21 | 10 |
Tachapol UdomaekPorter | Male | Agent | 240 | 0 | 240 | 20 | 11 |
Tanagorn RattanapanPorter | Male | Agent | 264 | 0 | 264 | 22 | 9 |
Traitod PrachayutMessenger | Male | Agent | 252 | 0 | 252 | 21 | 10 |
Wanpen SukjaiPorter | Female | Agent | 240 | 0 | 240 | 20 | 11 |
Wiroj SaengthongSenior Porter | Male | Senior | 240 | 0 | 240 | 20 | 11 |
Apichat MoonsriPorter | Male | Agent | 240 | 0 | 240 | 20 | 11 |
Duangjai PhetcharaPorter | Female | Agent | 264 | 0 | 264 | 22 | 9 |
Kanokwan PetchrungPorter | Female | Agent | 252 | 0 | 252 | 21 | 10 |
Kriangkrai SomboonPorter | Male | Agent | 240 | 0 | 240 | 20 | 11 |
| NNantana SrisukShift Supervisor | Female | Supervisor | 264 | 0 | 264 | 22 | 9 |
Naruemon ChaisriPorter | Female | Agent | 240 | 0 | 240 | 20 | 11 |
Nattapon SrichaiPorter | Male | Agent | 252 | 0 | 252 | 21 | 10 |
Phichit BoonchuPorter | Male | Agent | 240 | 0 | 240 | 20 | 11 |
Pornthip SaengdaoPorter | Female | Agent | 240 | 0 | 240 | 20 | 11 |
| PPrasit WongwanShift Supervisor | Male | Supervisor | 240 | 0 | 240 | 20 | 11 |
Ratchanee BoonrodSenior Porter | Female | Senior | 240 | 0 | 240 | 20 | 11 |
Sakda PhonsriSenior Porter | Male | Senior | 240 | 0 | 240 | 20 | 11 |
Somsak ThongmakPorter | Male | Agent | 252 | 0 | 252 | 21 | 10 |
Sunisa WongprasertPorter | Female | Agent | 240 | 0 | 240 | 20 | 11 |
Surasak InkaewPorter | Male | Agent | 252 | 0 | 252 | 21 | 10 |
Thawatchai KaewkhamPorter | Male | Agent | 240 | 0 | 240 | 20 | 11 |
Weerapong SaelimSenior Porter | Male | Senior | 252 | 0 | 252 | 21 | 10 |
Yupin NakprasertPorter | Female | Agent | 264 | 0 | 264 | 22 | 9 |
Ananya PongpanitchLogistics Supervisor Day Long07:00–19:00 Day Long07:00–19:00 Day OffAll day Day OffAll day Afternoon11:00–22:00 Afternoon11:00–22:00 Afternoon11:00–22:00 Day OffAll day Afternoon11:00–22:00 Day Long07:00–19:00 Afternoon11:00–22:00 Day Long07:00–19:00 Day OffAll day Day OffAll day Day OffAll day Day OffAll day Day Long07:00–19:00 Afternoon11:00–22:00 Afternoon11:00–22:00 Afternoon11:00–22:00 Afternoon11:00–22:00 Day Long07:00–19:00 Day OffAll day Day Long07:00–19:00 Day Long07:00–19:00 Afternoon11:00–22:00 Day Long07:00–19:00 Day OffAll day Day OffAll day Day OffAll day Afternoon11:00–22:00
Anucha BoonmeePorter Day OffAll day Mid Day10:00–18:00 Afternoon11:00–22:00 Day Long07:00–19:00 Day Long07:00–19:00 Day OffAll day Day OffAll day Night19:00–07:00 Day OffAll day Day OffAll day Day Long07:00–19:00 Day Standard08:00–18:00 Afternoon11:00–22:00 Day Long07:00–19:00 Day Standard08:00–18:00 Day Short09:00–17:00 Day Short09:00–17:00 Day Extended09:00–19:00 Day OffAll day Afternoon11:00–22:00 Day OffAll day Day OffAll day Afternoon11:00–22:00 Mid Morning10:00–20:00 Day OffAll day Day OffAll day Day Standard08:00–18:00 Day Standard08:00–18:00 Day Short09:00–17:00 Night19:00–07:00 Day OffAll day
Chaiwat InthongSenior Porter Mid Day10:00–18:00 Mid Day10:00–18:00 Day OffAll day Day Standard08:00–18:00 Day OffAll day Mid Day10:00–18:00 Day Extended09:00–19:00 Day Standard08:00–18:00 Day OffAll day Day OffAll day Day Extended09:00–19:00 Day Standard08:00–18:00 Day Standard08:00–18:00 Day Extended09:00–19:00 Night19:00–07:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Standard08:00–18:00 Day Standard08:00–18:00 Day Extended09:00–19:00 Day Standard08:00–18:00 Mid Day10:00–18:00 Day Extended09:00–19:00 Mid Day10:00–18:00 Night19:00–07:00 Day OffAll day Day OffAll day Night19:00–07:00 Day OffAll day Day Standard08:00–18:00
Jiraporn WongsaSenior Porter Day Extended09:00–19:00 Day OffAll day Day Standard08:00–18:00 Mid Day10:00–18:00 Night19:00–07:00 Day OffAll day Day Standard08:00–18:00 Day OffAll day Day Extended09:00–19:00 Mid Day10:00–18:00 Night19:00–07:00 Day OffAll day Mid Day10:00–18:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Extended09:00–19:00 Day Standard08:00–18:00 Mid Day10:00–18:00 Day Extended09:00–19:00 Mid Day10:00–18:00 Night19:00–07:00 Night19:00–07:00 Day OffAll day Day Standard08:00–18:00 Day Standard08:00–18:00 Only 1h rest before 08:00 (after 23 Dec) Day OffAll day Day Standard08:00–18:00 Night19:00–07:00 Day OffAll day Day OffAll day Mid Day10:00–18:00 Day Extended09:00–19:00
Kittipong ChaiyasitPorter Day OffAll day Day OffAll day Day Standard08:00–18:00 Day Short09:00–17:00 Day Extended09:00–19:00 Mid Morning10:00–20:00 Mid Morning10:00–20:00 Day OffAll day Day Short09:00–17:00 Day Short09:00–17:00 Day OffAll day Day OffAll day Day Standard08:00–18:00 Day OffAll day Mid Day10:00–18:00 Afternoon11:00–22:00 Day OffAll day Day OffAll day Day Long07:00–19:00 Day Standard08:00–18:00 Day OffAll day Day OffAll day Day Standard08:00–18:00 Mid Day10:00–18:00 Mid Morning10:00–20:00 Day Short09:00–17:00 Day OffAll day Day Long07:00–19:00 Day Standard08:00–18:00 Day Long07:00–19:00 Night19:00–07:00
Pongpisut PatamadechaPorter Day Long07:00–19:00 Afternoon11:00–22:00 Day OffAll day Day OffAll day Day Standard08:00–18:00 Day Standard08:00–18:00 Day Short09:00–17:00 Day Extended09:00–19:00 Mid Morning10:00–20:00 Day Short09:00–17:00 Afternoon11:00–22:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Short09:00–17:00 Day OffAll day Day OffAll day Mid Morning10:00–20:00 Mid Morning10:00–20:00 Mid Day10:00–18:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Short09:00–17:00 Day Short09:00–17:00 Day Extended09:00–19:00 Day Standard08:00–18:00 Day Standard08:00–18:00 Day Standard08:00–18:00 Day Short09:00–17:00 Day OffAll day
Siriporn ThongdeePorter Day OffAll day Day Standard08:00–18:00 Day Short09:00–17:00 Day Short09:00–17:00 Night19:00–07:00 Day OffAll day Day Short09:00–17:00 Day Standard08:00–18:00 Mid Day10:00–18:00 Afternoon11:00–22:00 Day Long07:00–19:00 Day OffAll day Day OffAll day Day Standard08:00–18:00 Day Short09:00–17:00 Day Short09:00–17:00 Day Short09:00–17:00 Day OffAll day Day Short09:00–17:00 Day OffAll day Mid Morning10:00–20:00 Mid Day10:00–18:00 Day Long07:00–19:00 Afternoon11:00–22:00 Day Long07:00–19:00 Day OffAll day Day OffAll day Day OffAll day Day Long07:00–19:00 Day OffAll day Day Short09:00–17:00
Tachapol UdomaekPorter Day Long07:00–19:00 Day Standard08:00–18:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Short09:00–17:00 Day Extended09:00–19:00 Mid Morning10:00–20:00 Mid Morning10:00–20:00 Day OffAll day Day OffAll day Mid Day10:00–18:00 Mid Morning10:00–20:00 Mid Morning10:00–20:00 Night19:00–07:00 Day OffAll day Day OffAll day Afternoon11:00–22:00 Day Long07:00–19:00 Day Standard08:00–18:00 Day Standard08:00–18:00 Day OffAll day Day OffAll day Day Short09:00–17:00 Day Extended09:00–19:00 Mid Morning10:00–20:00 Mid Morning10:00–20:00 Day OffAll day Day OffAll day Day OffAll day Afternoon11:00–22:00
Tanagorn RattanapanPorter Mid Morning10:00–20:00 Mid Morning10:00–20:00 Mid Day10:00–18:00 Day OffAll day Day OffAll day Afternoon11:00–22:00 Day Long07:00–19:00 Day Short09:00–17:00 Day OffAll day Day OffAll day Mid Day10:00–18:00 Afternoon11:00–22:00 Day Long07:00–19:00 Day Standard08:00–18:00 Day Extended09:00–19:00 Mid Morning10:00–20:00 Mid Morning10:00–20:00 Mid Day10:00–18:00 Day OffAll day Day OffAll day Mid Day10:00–18:00 Day OffAll day Mid Morning10:00–20:00 Day Short09:00–17:00 Day OffAll day Day OffAll day Mid Morning10:00–20:00 Mid Day10:00–18:00 Mid Day10:00–18:00 Day Short09:00–17:00 Mid Morning10:00–20:00
Traitod PrachayutMessenger Day Short09:00–17:00 Day Short09:00–17:00 Day Short09:00–17:00 Day OffAll day Day OffAll day Mid Morning10:00–20:00 Mid Day10:00–18:00 Afternoon11:00–22:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Short09:00–17:00 Mid Morning10:00–20:00 Day Short09:00–17:00 Day OffAll day Day OffAll day Day Standard08:00–18:00 Day Short09:00–17:00 Day Extended09:00–19:00 Mid Morning10:00–20:00 Day OffAll day Day OffAll day Day OffAll day Mid Morning10:00–20:00 Mid Morning10:00–20:00 Mid Day10:00–18:00 Day Extended09:00–19:00 Mid Morning10:00–20:00 Day OffAll day Day Standard08:00–18:00 Day Short09:00–17:00
Wanpen SukjaiPorter Day Standard08:00–18:00 Day Short09:00–17:00 Day Short09:00–17:00 Day Short09:00–17:00 Day OffAll day Day OffAll day Day Long07:00–19:00 Day Long07:00–19:00 Afternoon11:00–22:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Standard08:00–18:00 Day Short09:00–17:00 Day Short09:00–17:00 Day Short09:00–17:00 Mid Day10:00–18:00 Day OffAll day Day OffAll day Day Long07:00–19:00 Day Long07:00–19:00 Afternoon11:00–22:00 Day OffAll day Day OffAll day Mid Day10:00–18:00 Mid Day10:00–18:00 Day Short09:00–17:00 Day Short09:00–17:00 Day OffAll day Day OffAll day Day OffAll day
Wiroj SaengthongSenior Porter Day Standard08:00–18:00 Day Extended09:00–19:00 Mid Day10:00–18:00 Night19:00–07:00 Day OffAll day Day OffAll day Night19:00–07:00 Day OffAll day Day Standard08:00–18:00 Day Extended09:00–19:00 Day Standard08:00–18:00 Night19:00–07:00 Day OffAll day Day Standard08:00–18:00 Mid Day10:00–18:00 Mid Day10:00–18:00 Night19:00–07:00 Day OffAll day Day OffAll day Mid Day10:00–18:00 Day OffAll day Mid Day10:00–18:00 Day OffAll day Day OffAll day Day Standard08:00–18:00 Day Extended09:00–19:00 Mid Day10:00–18:00 Night19:00–07:00 Day OffAll day Day OffAll day Mid Day10:00–18:00
Apichat MoonsriPorter Day Extended09:00–19:00 Mid Morning10:00–20:00 Mid Morning10:00–20:00 Mid Day10:00–18:00 Day OffAll day Day OffAll day Mid Day10:00–18:00 Mid Day10:00–18:00 Day Standard08:00–18:00 Day Standard08:00–18:00 Day OffAll day Day OffAll day Day Extended09:00–19:00 Mid Morning10:00–20:00 Mid Morning10:00–20:00 Night19:00–07:00 Day OffAll day Day OffAll day Afternoon11:00–22:00 Day Long07:00–19:00 Day Long07:00–19:00 Day Standard08:00–18:00 Day OffAll day Day OffAll day Day Short09:00–17:00 Day Standard08:00–18:00 Mid Day10:00–18:00 Afternoon11:00–22:00 Day OffAll day Day OffAll day Day OffAll day
Duangjai PhetcharaPorter Day Standard08:00–18:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Short09:00–17:00 Day Short09:00–17:00 Mid Morning10:00–20:00 Mid Morning10:00–20:00 Day OffAll day Day OffAll day Mid Morning10:00–20:00 Day Short09:00–17:00 Day Long07:00–19:00 Day Long07:00–19:00 Day Standard08:00–18:00 Day OffAll day Day OffAll day Day Short09:00–17:00 Day Short09:00–17:00 Day Extended09:00–19:00 Day Extended09:00–19:00 Mid Morning10:00–20:00 Day OffAll day Day Long07:00–19:00 Day Standard08:00–18:00 Day Standard08:00–18:00 Night19:00–07:00 Day OffAll day Mid Morning10:00–20:00 Mid Morning10:00–20:00 Day OffAll day
Kanokwan PetchrungPorter Night19:00–07:00 Day OffAll day Day OffAll day Day Standard08:00–18:00 Day Short09:00–17:00 Day Extended09:00–19:00 Afternoon11:00–22:00 Day Short09:00–17:00 Day OffAll day Mid Day10:00–18:00 Mid Day10:00–18:00 Day Short09:00–17:00 Day Short09:00–17:00 Day OffAll day Day OffAll day Mid Day10:00–18:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Short09:00–17:00 Day Short09:00–17:00 Day Short09:00–17:00 Day Short09:00–17:00 Day OffAll day Day OffAll day Day Short09:00–17:00 Day Short09:00–17:00 Day Extended09:00–19:00 Afternoon11:00–22:00 Day OffAll day Mid Morning10:00–20:00
Kriangkrai SomboonPorter Mid Morning10:00–20:00 Mid Day10:00–18:00 Day OffAll day Day OffAll day Mid Day10:00–18:00 Day Long07:00–19:00 Day Standard08:00–18:00 Day Standard08:00–18:00 Day OffAll day Day OffAll day Day Short09:00–17:00 Day Standard08:00–18:00 Day Short09:00–17:00 Night19:00–07:00 Day OffAll day Day OffAll day Mid Day10:00–18:00 Day Long07:00–19:00 Day OffAll day Mid Morning10:00–20:00 Mid Morning10:00–20:00 Mid Day10:00–18:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Long07:00–19:00 Day OffAll day Day OffAll day Mid Morning10:00–20:00 Mid Day10:00–18:00 Day Long07:00–19:00
Naruemon ChaisriPorter Day Short09:00–17:00 Day OffAll day Day OffAll day Day Extended09:00–19:00 Afternoon11:00–22:00 Day Long07:00–19:00 Day Standard08:00–18:00 Day OffAll day Day OffAll day Day Short09:00–17:00 Day Short09:00–17:00 Day Extended09:00–19:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Extended09:00–19:00 Mid Morning10:00–20:00 Mid Day10:00–18:00 Mid Day10:00–18:00 Day OffAll day Day OffAll day Day Long07:00–19:00 Mid Day10:00–18:00 Day Long07:00–19:00 Day Long07:00–19:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Short09:00–17:00 Day OffAll day Day Short09:00–17:00
Nattapon SrichaiPorter Mid Day10:00–18:00 Day Long07:00–19:00 Day Standard08:00–18:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Short09:00–17:00 Day Short09:00–17:00 Day Short09:00–17:00 Day OffAll day Day OffAll day Mid Morning10:00–20:00 Mid Day10:00–18:00 Afternoon11:00–22:00 Day OffAll day Day OffAll day Day Extended09:00–19:00 Mid Morning10:00–20:00 Mid Day10:00–18:00 Day Short09:00–17:00 Day Short09:00–17:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Standard08:00–18:00 Day Short09:00–17:00 Day Long07:00–19:00 Day OffAll day Day OffAll day Day Short09:00–17:00 Day Extended09:00–19:00
Phichit BoonchuPorter Day OffAll day Day OffAll day Day Long07:00–19:00 Day Standard08:00–18:00 Day Standard08:00–18:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Long07:00–19:00 Day Long07:00–19:00 Mid Morning10:00–20:00 Mid Day10:00–18:00 Day OffAll day Day OffAll day Mid Morning10:00–20:00 Mid Morning10:00–20:00 Day Standard08:00–18:00 Day Standard08:00–18:00 Day OffAll day Day OffAll day Day Short09:00–17:00 Day Extended09:00–19:00 Mid Morning10:00–20:00 Night19:00–07:00 Day OffAll day Day OffAll day Afternoon11:00–22:00 Day Long07:00–19:00 Day Long07:00–19:00 Day Standard08:00–18:00 Day OffAll day
Pornthip SaengdaoPorter Day OffAll day Day Extended09:00–19:00 Mid Morning10:00–20:00 Mid Morning10:00–20:00 Mid Day10:00–18:00 Day OffAll day Day OffAll day Day Long07:00–19:00 Day Long07:00–19:00 Day Standard08:00–18:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Extended09:00–19:00 Day Long07:00–19:00 Day Long07:00–19:00 Day OffAll day Day OffAll day Mid Morning10:00–20:00 Mid Day10:00–18:00 Mid Day10:00–18:00 Day Standard08:00–18:00 Day Standard08:00–18:00 Day OffAll day Day OffAll day Mid Morning10:00–20:00 Mid Day10:00–18:00 Mid Day10:00–18:00 Night19:00–07:00 Day OffAll day Day OffAll day
Ratchanee BoonrodSenior Porter Day OffAll day Day Standard08:00–18:00 Day Extended09:00–19:00 Day Extended09:00–19:00 Day Standard08:00–18:00 Night19:00–07:00 Day OffAll day Day Extended09:00–19:00 Mid Day10:00–18:00 Night19:00–07:00 Day OffAll day Day OffAll day Day OffAll day Day OffAll day Day Standard08:00–18:00 Day OffAll day Mid Day10:00–18:00 Mid Day10:00–18:00 Day Extended09:00–19:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Extended09:00–19:00 Day Standard08:00–18:00 Day OffAll day Night19:00–07:00 Day OffAll day Day Extended09:00–19:00 Mid Day10:00–18:00 Day Standard08:00–18:00 Night19:00–07:00 Day OffAll day
Sakda PhonsriSenior Porter Night19:00–07:00 Day OffAll day Day OffAll day Day OffAll day Day Extended09:00–19:00 Day Standard08:00–18:00 Mid Day10:00–18:00 Night19:00–07:00 Day OffAll day Day Standard08:00–18:00 Mid Day10:00–18:00 Day Extended09:00–19:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Standard08:00–18:00 Day Standard08:00–18:00 Day Extended09:00–19:00 Night19:00–07:00 Day OffAll day Night19:00–07:00 Day OffAll day Day OffAll day Mid Day10:00–18:00 Day Extended09:00–19:00 Mid Day10:00–18:00 Day OffAll day Day Standard08:00–18:00 Day Extended09:00–19:00 Day Standard08:00–18:00 Day OffAll day
Somsak ThongmakPorter Day Short09:00–17:00 Day Short09:00–17:00 Day OffAll day Day OffAll day Day Short09:00–17:00 Day Short09:00–17:00 Day OffAll day Day OffAll day Day Extended09:00–19:00 Mid Morning10:00–20:00 Day Standard08:00–18:00 Day Long07:00–19:00 Day OffAll day Day Short09:00–17:00 Day OffAll day Day OffAll day Day Long07:00–19:00 Day Standard08:00–18:00 Day Short09:00–17:00 Day Short09:00–17:00 Day OffAll day Mid Morning10:00–20:00 Mid Day10:00–18:00 Mid Day10:00–18:00 Day OffAll day Day OffAll day Day Short09:00–17:00 Day Short09:00–17:00 Day Extended09:00–19:00 Afternoon11:00–22:00 Day Standard08:00–18:00
Sunisa WongprasertPorter Afternoon11:00–22:00 Day Long07:00–19:00 Day Long07:00–19:00 Day Long07:00–19:00 Day OffAll day Day OffAll day Day OffAll day Mid Day10:00–18:00 Day Standard08:00–18:00 Day Extended09:00–19:00 Day Extended09:00–19:00 Day OffAll day Day OffAll day Mid Day10:00–18:00 Mid Day10:00–18:00 Day Long07:00–19:00 Day OffAll day Day OffAll day Day Standard08:00–18:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Extended09:00–19:00 Day OffAll day Mid Day10:00–18:00 Afternoon11:00–22:00 Day Long07:00–19:00 Night19:00–07:00 Day OffAll day Day Long07:00–19:00 Day Standard08:00–18:00
Surasak InkaewPorter Day OffAll day Day OffAll day Mid Day10:00–18:00 Afternoon11:00–22:00 Day Long07:00–19:00 Day Standard08:00–18:00 Day OffAll day Day OffAll day Day Short09:00–17:00 Mid Morning10:00–20:00 Day OffAll day Day OffAll day Mid Day10:00–18:00 Mid Day10:00–18:00 Afternoon11:00–22:00 Mid Day10:00–18:00 Day Long07:00–19:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Standard08:00–18:00 Day Short09:00–17:00 Day Short09:00–17:00 Day Standard08:00–18:00 Day Short09:00–17:00 Day OffAll day Day OffAll day Mid Morning10:00–20:00 Mid Day10:00–18:00 Mid Morning10:00–20:00 Mid Day10:00–18:00
Thawatchai KaewkhamPorter Day OffAll day Day OffAll day Day Extended09:00–19:00 Mid Morning10:00–20:00 Mid Morning10:00–20:00 Mid Day10:00–18:00 Day OffAll day Day OffAll day Mid Day10:00–18:00 Mid Day10:00–18:00 Day Short09:00–17:00 Mid Morning10:00–20:00 Day OffAll day Day OffAll day Day OffAll day Day Standard08:00–18:00 Day Short09:00–17:00 Day Short09:00–17:00 Night19:00–07:00 Day OffAll day Afternoon11:00–22:00 Day Long07:00–19:00 Day Long07:00–19:00 Day Standard08:00–18:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Short09:00–17:00 Day OffAll day Mid Day10:00–18:00 Day Long07:00–19:00
Weerapong SaelimSenior Porter Day OffAll day Night19:00–07:00 Night19:00–07:00 Day OffAll day Mid Day10:00–18:00 Day Extended09:00–19:00 Day OffAll day Mid Day10:00–18:00 Night19:00–07:00 Day OffAll day Day OffAll day Mid Day10:00–18:00 Day Extended09:00–19:00 Mid Day10:00–18:00 Day Extended09:00–19:00 Day Extended09:00–19:00 Day OffAll day Night19:00–07:00 Day OffAll day Day OffAll day Day Standard08:00–18:00 Day Extended09:00–19:00 Day Standard08:00–18:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Standard08:00–18:00 Day Extended09:00–19:00 Mid Day10:00–18:00 Day Extended09:00–19:00 Night19:00–07:00
Yupin NakprasertPorter Mid Day10:00–18:00 Day OffAll day Day OffAll day Mid Day10:00–18:00 Mid Morning10:00–20:00 Mid Day10:00–18:00 Night19:00–07:00 Day OffAll day Day OffAll day Day Long07:00–19:00 Day Standard08:00–18:00 Day Long07:00–19:00 Day Short09:00–17:00 Day OffAll day Day Long07:00–19:00 Day Standard08:00–18:00 Afternoon11:00–22:00 Day Long07:00–19:00 Day Standard08:00–18:00 Day OffAll day Day OffAll day Day Short09:00–17:00 Day Short09:00–17:00 Day Extended09:00–19:00 Afternoon11:00–22:00 Day Long07:00–19:00 Day OffAll day Day OffAll day Day Short09:00–17:00 Day Extended09:00–19:00 Mid Day10:00–18:00 Run Information
ConstraintsAll constraints met
Supervisor shortfall0
Senior shortfall0
Agent shortfall0
Leave violation0
Fixed assignment0
Forbidden assignment0
Gender restriction0
Rest between shifts0
Weekly rest0
Skill floor shortfall0
Constraints2 constraints unmet
Supervisor shortfall0
Senior shortfall2
Agent shortfall1
Leave violation0
Fixed assignment0
Forbidden assignment0
Gender restriction0
Rest between shifts0
Weekly rest0
Skill floor shortfall0
ConstraintsAll constraints met
Supervisor shortfall0
Senior shortfall0
Agent shortfall0
Leave violation0
Fixed assignment0
Forbidden assignment0
Gender restriction0
Rest between shifts0
Weekly rest0
Skill floor shortfall0
Constraints1 constraint unmet
Supervisor shortfall0
Senior shortfall0
Agent shortfall0
Leave violation0
Fixed assignment0
Forbidden assignment0
Gender restriction0
Rest between shifts1
Weekly rest0
Skill floor shortfall0
Manage Assignment
Jiraporn Wongsa · 24 Dec
Day Long07:00–19:00Day Standard08:00–18:00Day Short09:00–17:00Day Extended09:00–19:00Mid Morning10:00–20:00Mid Day10:00–18:00Afternoon11:00–22:00Night19:00–07:00 Day OffAll day2 constraints unmet
This run left 2 constraints unmet. Roster can try once more with a deeper search, taking roughly three to four times as long as the run you just waited for.
Search deeper
Optimizing...
Looked over the inputs — no structural bottleneck
Starting from a baseline schedule, then refining it step by step
Passed the 25%-better mark
Passed the 50%-better mark
Passed the 75%-better mark
Progress stalled — shaking things up to explore new options
Finished refining the schedule
Run in background
Roster does not trust its own optimizer, and neither should the manager. It never sums a roster up in one score; it names the problems instead, a senior short on the 12th, too little rest before a morning. When it falls short of her rules it says so, and offers one deeper search rather than quietly giving up. The machine’s roster is kept apart from her edits, so she can always go back to either. It is a tool for a human decision, not an automation that removes one.
Every shift covered
The supervisors, seniors and staff each shift needs, set for every day of the week.
Rest
Hours of rest between shifts, and days off in every week, as the team’s policy sets them.
What people asked for
Days of leave kept, and shifts someone must or must not work.
The Evaluator
When the manager fixes the plan by hand, the Evaluator rechecks it and names every rule it now breaks.
Each month the manager chooses what Roster must not give way on. Some rules hold in every mode: leave granted, rest between shifts, a day off each week, the shifts someone must or must not work. The mode decides what comes first after them.
Coverage
Roster’s default. Every shift staffed exactly as asked, in each role: too many is as wrong as too few. And no one works too many extra shifts in a row.
Balanced
Nothing comes first. Beyond the rules every mode keeps, each concern, a short-staffed shift included, is weighed against the others.
Well-Being
The team’s health first: no one works too many extra shifts in a row. Everything else is weighed after it.
Service Quality
The most hands on the floor. No shift may be short, and more staff and seniors than asked are welcome on the busiest shifts; supervisors stay exact.
It has already planned a real porter team’s month, about thirty people, from the engine straight to the spreadsheet they work from. Three to five days of a manager’s work became ten minutes. That is what we mean by the 10X improvement philosophy we talk about in Join us: not the same steps done faster, but the work done differently.
Roster is an experiment, and a very promising one. Its engine and the web application a manager plans in are built. Still to come: signing in, a view for the team themselves, the mobile app, planning by each person’s number of shifts, and keeping cost down, which it already calculates but does not yet optimize.
Next, the plan meets the work. Roster is to work natively with
Dispatcher and
People, so that a month’s staffing rests on the demand the hospital really has: how many jobs come in, at which hours, and who is on duty to take them. Each application becomes more complete on its own, and more powerful together.

If someone in your hospital spends days on next month’s roster, we’d like to hear how it is done today.
One and 100 average 50.5. Nobody waited 50.5 minutes.
Ask a hospital how its porters did last month and the answer is one number: the average response time. Managers ask for it, and executives ask for it. Take two patients, one answered in 1 minute and one in 100. Their average is 50.5, a wait neither of them had.
An average also forgets what the hour was like. Here are two hours in one hospital, every dot a job. Both averaged 10 minutes. On a monthly report they are the same hour.
Tuesday 30 June 2026, 10:00 73 jobs, 13 people
Saturday 8 August 2026, 11:00 58 jobs, 13 people
26% more work
Tuesday carried 73 jobs and Saturday 58, with 13 people each time. The average did not move.
A bigger share waited long in the quieter hour
Saturday had fewer jobs, yet 28% of them waited over 15 minutes (16 of 58 jobs), while Tuesday, with more jobs, had only 19% waiting that long.
A wait nobody had
On Saturday no job took 10 to 11 minutes. Jobs were either quicker or slower, and the average landed in the gap between them.
So people set a target: answer every job within so many minutes. But 11 minutes at three in the morning, with two porters and two jobs waiting, is fine. 11 minutes at 10:00, with a full team and 40 jobs in the queue, is a service failing. One number cannot be fair to both.
So we handed the problem to our interns.


They asked a different question, and we helped shape it: what has this team done before, in the same situation? Take Saturday 8 August at 11:00: 58 jobs among 13 people. The search goes back through the past year to every Saturday at 11:00 and keeps the one with the closest job load, the jobs each person carried. If hours tie, the number of jobs decides, then the pressure, the minutes of work asked for against the minutes of people available, and last, how recent it was.
Jobs per person, every Saturday at 11:00
That hour is the benchmark, and every hour finds its own, which is why we call the KPI rolling. It takes a division, a search and a percentile: simple mathematically, and very practical. And it is new. We believe it is a better way to deeply understand how your operations run.
The benchmark’s 60th percentile, or P60, the time 60% of its jobs were answered within, becomes the bar. Each job now either met it or did not, and the share that met it grades the hour. Here are the same two hours again.
Tuesday 30 June 2026, 10:00 Under Controlled
63 / 73 met it
Saturday 8 August 2026, 11:00 Critical
17 / 58 met it
The same 10-minute average, and opposite truths. Saturday’s benchmark had answered within 6:01, and only 17 of 58 jobs did. That Tuesday was measured against a hard hour, 16:07, and 63 of 73 made it.
Under Controlled
More than 75% of its jobs met the bar.
Elevated
50% to 75%.
Stressed
30% to under 50%.
Critical
Under 30%.
An hour that does exactly what its benchmark did lands near 60%, in Elevated. Under Controlled means beating your own past. Here is one week, hour by hour, and no single number could have told you this.
Click a level to cross it out.
Hospitals are places of habit. Every day of this week rose and fell in almost the same shape, so the shape tells you little. What matters is the colour: the hours that did worse than this team has done before, in the same situation. The coloured line is the Monday above. At 11:00, 58 jobs were Critical. At 14:00, 59 jobs were Stressed. Almost the same traffic, and a different hour.
Jobs in each hour, Monday 3 August 2026: 638 jobsAverage response time, Monday 3 August 2026: 16:33
Now press Average only. Monday becomes one tall spike, and the stressed afternoon disappears under a 10-minute target. No fixed target solves this: six minutes flags half the week, and 10 misses half the trouble.
If you take one thing from this page, take these to your next report.
Who is hidden in it?
An average hides the person who waited longest. Ask for the shape, not the middle.
What is it compared with?
A number means nothing alone. Ask what it is being held against, and who chose that.
Was that a fair comparison?
Same hour of the week, same load? If not, you are comparing a quiet night with a full morning.
Every figure on this page comes from Mu Hospital, the invented hospital Class 26 build against: 23 porters, 50 places, and nobody real. Rolling KPI is what Mu, our assistant, explains. We could not be prouder of Krittinee and Preawnapat.
To know when your operations are likely to break gives you a better chance to prepare a better plan. That is why this experiment complements Roster.
Every movable device, found in minutes.
“Where is the infusion pump?” In many hospitals that question sends a nurse searching through the wards. Things puts small Bluetooth tags on movable equipment, from infusion pumps to wheelchairs and beds, so where each one is, is known in real time.
Staff stop searching and get back to their patients, and the hospital learns how much equipment it really uses, so it buys and maintains only what it needs.
Each device wears a small Bluetooth tag. The hospital’s own Wi-Fi access points, from Aruba, Cisco or Huawei, already listen for Bluetooth, so they hear every tag as it passes, and Things knows where each device is, with no one scanning it. There is no second network to build: it is quicker and costs less to set up, adds no new risk for IT, and stays as easy to manage and to grow as the network it runs on.
1
Things works with the access points the hospital already runs, from Aruba, Cisco or Huawei: they hear Bluetooth as well as Wi-Fi.
2
In the Things app on a phone, each tag is bound to its device.
3
The tag goes on the pump. From then on the access points hear it wherever it goes, with no one scanning it.
4
Scan with a phone to see every device around you and its status, or find any one of them on the web.
Things keeps watch over every movable device, so no one has to search for one. Its web console shows where each device is now, how much each kind is used, and how many each department holds against what it needs. A device is found in seconds, and the hospital puts the equipment it owns to work instead of buying more. Below, the console plays on its own: the devices by category, a request for pumps carried from the equipment center to the Children Center, and one of those pumps found by search.
Knowing where each device is, is only the start. Every tool below works from the same live picture of the hospital’s equipment: keeping the inventory right, sharing devices between departments, and keeping each one ready for use.
01
Multiple categories
Every kind of high-value, movable equipment: infusion pumps, ultrasound machines, beds, wheelchairs and more.
02
Real-time information
Where each device is now, or was last seen, and how long it has been in use; how many of each kind every department holds.
03
Par settings
Set a par for each zone, and watch use and availability against it, by zone and by department.
04
Borrow and return
Share equipment between departments: see what is free, and request it from the equipment center.
05
Patient mapping
Assign a device to a patient to time its use; release it when done, and the service charge is worked out.
06
Utilization tracking
How much each device is really used, judged by where it is, against the hours set as its target.
07
BLE tags
Bind a tag to a device in the Things app, and check its ID, signal strength and battery.
08
Quick search
Find any device in a moment, with where it is and its status, and the nearest one when you need one.
09
Assets near me
Scan with your phone to see every device around you, and check each one’s status from where you stand.
10
Asset history
Every device’s whole story: where it has been, for how long, who used it, and when it was serviced.
11
Asset reports
Inventory and profiles, use by department, borrow and return requests, and more.
12
Asset insights
A live dashboard of every device by status, in use, not in use and more, in graphs.
Once every device is in sight, a hospital can run its equipment differently: less time searching, more use from each device, fewer devices to hold, and less to spend on them.
Search time
10×
faster to find a device, giving nurses time back for the work that matters.
Nurses spend as much as 72 minutes a shift searching for devices.
Utilization
up to 70%
of each device’s time in use: the equipment the hospital owns, put to work.
Medical devices, movable ones above all, are in use as little as 30% of the time.
Inventory size
−30%
fewer devices to hold, when each one is used more.
Most hospitals hold at least twice the devices they really need.
Purchasing budget
−15%
less to spend on buying or renting medical devices.
Without data, managers cannot decide well what to buy, or when.
These figures are possibilities, not results: what can change once every device is in sight, not what we have measured in a hospital. How much of it a hospital sees depends on where it starts.
Things is still being built, and we’d like to build it with hospitals. If this sounds like yours, tell us how your devices move today, and where your staff search for them.
Understand how work flows through people.
People knows when each person on a team is where the work is: on a ward round, in the OPD, at a case review. A small badge does it, with nothing to press and nothing to fill in.
General Medicine TeamToday · 10:45
Ward Rounding(0 more)
Ward 7
Nalintra Srisakorn07:04–08:01 · 57m
Ward Rounding(0 more)
Ward 5
Darika Phumiphat07:34–08:49 · 1h 15m
Daily Examination – OPD(0 more)
Outpatient Center
Niran Phongchai08:05 · 2h 40m
Critical Care Rounding(0 more)
CCU
Kamala Ratchanee08:36–09:20 · 44m
Consulting and Prescription(0 more)
Ward 7
Nalintra Srisakorn09:07–09:44 · 37m
Ward Rounding(1 more)
Ward 7
Kamala Ratchanee09:38–10:26 · 48m
Case Review Session(0 more)
Medical Office
Manit Sorasak10:09 · 36m
Daily Examination – OPD(0 more)
Outpatient Center
Phuwadon Rattanakorn10:38 · 7m
Each card is a presence: five minutes or more in a zone, such as a ward, and the work done in its areas. Places are named to the ward or the room, never a point on a map, and live positions stay masked until someone asks to see one, with a record of who asked.
Nobody checks in. A badge is seen by the access points it passes, and People’s rule does the rest: five minutes in a zone, such as a ward, begin a presence, and ten minutes away close it. Inside the zone, the time in each Area of Interest is taken to be the work bound to that area. Here is Dr. Kamala’s ward round this morning, as People saw it.
Kamala RatchaneeConsultant10:45
Ward 7Internal Medicine
Ward 7 – Patient Rooms
Ward 7 – Nurse Station
Presence Summary
Ward 7Internal Medicine

2 areas visited48m
People is about individuals, and we don’t pretend otherwise. So we built it to be fair to them. Live places are masked by default. Seeing one takes a reason, and every look is recorded: who looked, at whom, why and when.
General Medicine Team10:45
NameBadgeLocationLast seen
Anongnart VichitkornDoctor OnlineBLE badge •••••• Just now
Darika PhumiphatIntern OfflineBLE badge •••••• 1h 56m ago
Jirayu VichaiDoctor OnlineBLE badge •••••• Just now
Kamala RatchaneeConsultant OnlineBLE badge •••••• Just now
Manit SorasakConsultant OnlineBLE badge •••••• Just now
Nalintra SrisakornDoctor OfflineBLE badge •••••• 1h 1m ago
Niran PhongchaiDoctor OnlineBLE badge Outpatient CenterInternal Medicine Just now
Phuwadon RattanakornIntern OnlineBLE badge •••••• Just now
See Niran Phongchai’s location
ReasonUrgent consult, Ward 5
This request is recorded.Request
Location access
People starts from one assumption: where a person is, and for how long, is sensitive. So privacy isn’t a policy written beside the system and hoped for. It is built into how the system behaves, how its records are reached, and how much of them anyone can see. Six protections do that work, on every screen, every day.
01
Stealth Mode
Live places are masked by default. Seeing one is a request, never a glance.
02
Location access audit trail
Every look at a place is recorded: who looked, at whom, why and when.
03
Delayed display
Records can appear only after a delay, so they serve planning, not watching.
04
Role-based visibility
Each role sees what its work needs, and no more.
05
Non-observant by default
Nothing is recorded until the hospital decides what to observe, and why: here, Ward 9’s rooms, for Ward Rounding.
06
Signals, not scores
A prompt to ask, never a verdict: each person against their own usual, never against colleagues.
People helps a hospital see how time, movement and activity unfold across its teams and spaces. Beyond one team’s morning, these are the screens that show the whole of it, as People’s own web console has them.
The Presence screen lists every stay in a zone: who, where, when, for how long, and the work it held. Records appear only twelve hours after they end, so they serve planning, not watching. Here, last night’s stay arrives as its twelve hours pass.
Each zone keeps its traffic: how long it was occupied, by what kind of work, in which of its areas. This is Ward 7 this morning, with Dr. Nalintra’s and Dr. Kamala’s rounds inside it.
Recurring work is defined once, binding teams and zones together. Here is Ward Rounding today across every team, with the time People can’t be sure of kept apart, never guessed.
A zone follows how the work is organized, not the lines of the floor plan. Rooms are grouped into Areas of Interest, each bound to its work. Corridors belong to none, so they are never observed.
The Real Time Dashboard counts the hospital as it is now: who is in a zone, which zones are busy or empty, and how today’s time has been spent, hour by hour. Numbers, not names.
Doctors are where this page began, not where People ends. Every role in a hospital moves differently, works under different constraints, and needs its own understanding of presence and activity. One system serves them all, each in a workspace of its own.

Doctors
Ward rounds, consultations and on-call duty, without interrupting care.

Nurses
The coordination and movement across the ward that shape a day’s workload.

Patients
Where it is right to: less waiting, safer and more predictable journeys.

Technicians
Technical work across wards and service areas, answered faster.

Housekeeping
Cleaning routines and coverage, without manual reporting.

Security
Sensitive and restricted areas covered, and ready to respond.
Linking a person to a badge takes a phone and a moment: choose the member, find the badge nearby, assign it. No forms and no specialist tools, and it can be changed or removed whenever assignments change. Here is Dr. Mana’s first morning.

Specialist, General Medicine Team
Bound today at 08:02
Observation rules
Ward Rounding
G General Medicine TeamWard 7Patient Rooms
G General Medicine TeamWard 7VIP Patient Rooms
G General Medicine TeamWard 5Patient Rooms
Consulting and Prescription
G General Medicine TeamWard 7Nurse Station
G General Medicine TeamWard 5Nurse Station
Case Review Session
G General Medicine TeamMedical OfficeConference Room 2
Daily Examination – OPD
Mana MorakodpunOutpatient CenterExam Rooms
People is at work in a hospital now, every day, reading each badge by its rules and keeping every stay. This is what it has captured so far, and it is still counting.

If this sounds like your hospital, we’d like to hear how your teams work today.
The rest of the system
The foundation the others stand on.
Admin is where a hospital’s IT team builds and runs what every Application stands on: its places, its maps, its people and its devices. Each is set up once, here, and every Application works from the same picture, so nothing is entered twice and nothing disagrees.
Think in one platform, not in separate products. A new Application starts out already knowing the hospital.
Here the hospital’s IT manager gets a new floor ready. He uploads its plan and draws a room on it, places one of the Wi-Fi access points the hospital already has, and sees which department works there and how its people sign in.
© OpenStreetMap contributors
Behind that screen are four things Admin keeps for the whole hospital: its places, its maps, its people and its devices. Each is set up once, here, and every Application works from it.
A hospital’s places are written down once and used everywhere, so when two Applications name a room, they mean the same room.
Many sites
Every hospital in a group under one organisation, all in view from one place.
As the buildings are
Sites, buildings, floors, zones and rooms in one structure that mirrors the real layout.
For each Application
Each place assigned to the Applications that work there, with no copies to keep in step.
Each floor is drawn on real-world coordinates, and the routes between places on top: corridors, lifts and stairs. That is how Dispatcher knows how far each porter really is from a job, not as the crow flies but by the shortest way there.
Floor plans
Every floor on real-world coordinates (WGS 84), so each place has an exact position.
Routes
Corridors, lifts and stairs drawn and joined on the plans, in the browser.
Shortest path
The real distance between any two places, which Dispatcher uses to rank who is nearest to a job.
Everyone who uses Mutrack has one account, kept for the whole organisation.
One account
Each person signs in once and reaches every Application they may use.
Permissions
Which Applications each person may use, and what they may do in each.
Departments
Places grouped into departments, so each department’s activity is seen together.
Mutrack’s locators, and the hospital’s own Wi-Fi access points, report what they hear. Admin keeps track of every one.
From start to finish
Add a device, update it, bind it to a place, and unbind it.
Live status
Every device’s status as it is now, with a notice when something goes wrong.
One device, many Applications
A single device serves several Applications: what it hears goes on to each one that needs it.

Who is nearest to a job, by the real way there.

Where each person is, from the same locators.

Admin
Places, maps, people and devices.

Where each device is, from the same tags.
Every Mutrack Application stands on Admin. If you’re planning one, tell us about your hospital: its sites, its buildings, and the Wi-Fi it already has.
Smart Healthcare and Smart Hospital, Loghealth, Bangkok.
How hospitals can adopt technology strategically to cut costs, save time and work sustainably. Why the only option going forward is to become better decision-makers, and why a 10X improvement is easier than 20%.
Hospital Information Management for Logistics System.
What real-time location gives a hospital: just four things. What, who, where and when. Ordinary, until they are real-time, in context, and told as stories.
I lead, learn, and build with vision, love and care.
Then again, with this question - Who am I?
It is not about a rank, a position or a level of mine. But who am I really?
With a quick deliberation with myself, it turns out I am just a man who tries to do good things. I am just a man who believes that together is better. I am just a man who wants to bring advancement to this country and hopefully to this world. All in all, I am just a man who got lucky enough to be on the path toward that. Thanks to my fantastic teammates.
Instead of seeing myself as a CEO, I consider myself a problem solver because that is what I do everyday. My teammates and I, we try to tackle hard problems. We try to fight tough obstacles. We try to bring our ideas to life. Because we really believe that what we are doing will make life of so many people better.
I am a part of a company called Mutrack - a Thai company specialized in tracking and positioning technologies. Through our work, we blend software with hardware. We bring together online and offline. We combine efficiency and simplicity. We create a platform that will help our customers understand more about their operations so that they can make fast and smarter decisions.
At Mutrack, we believe that we together can and will make a world class product. We put faith in individuality. We care more about human than numbers. We love sustainability and calmness. We give respect to the people around us and to the work that we do. And we are looking for someone who believes in the same things. Someone who shares the same values. Someone who wants to learn and do things differently.
If you think you might be that someone, you can find out more by contacting me here.
It doesn’t matter what your specialty and background are, it will be my honor to share the whole story with you. We have a grand plan and we need your help.

Thank you for your message to Mutrack. We'll be in touch soon.
94 Soi Sukhumvit 23 (Prasarnmitr), Sukhumvit Road, Klongtoey Nua, Watthana, Bangkok, Thailand
Let us know before you come, and we'll be ready for you.
Open in Maps ↗© OpenStreetMap contributors
Everyone wants software that feels tailor-made. A tweak here, a custom report there—it seems harmless. But over time, these one-off changes quietly erode product stability, increase support debt, and slow down innovation. This article explores the hidden costs of software customization and makes the case for building flexible systems instead—systems that empower users without compromising structure, speed, or long-term scalability. If you’re building platforms that are meant to last, this is a call to choose clarity over compromise and flexibility over fragmentation.
Piyorot Piyachan21 August 2025
Everyone wants software that feels like it was made just for them.
We understand that instinct. It comes from a good place—a desire to feel seen, supported, and empowered by the tools we use every day. Whether it’s a slightly different workflow, a new kind of report, or a color scheme that aligns with brand guidelines, customization often begins with a small request, a quick fix, or a well-intentioned “just for us” feature. It feels harmless. Helpful, even. But beneath that friendly surface lies something more dangerous: a path that, if followed too often, leads to long-term pain, both for the product and for the people who rely on it.
Customization, in its pure form, is the act of altering the core product to meet the unique needs of a specific user or customer. And while it sounds like a mark of great customer service or deep empathy, it often becomes the opposite. It introduces complexity, undermines maintainability, and eventually erodes trust—not because something broke, but because no one knows what will break next. When every customer ends up on a different version of the same product, the result is no longer a platform—it’s a collection of one-offs held together by hope and duct tape.
Why saying yes to every request slowly breaks the very thing you’re trying to build.
In this piece, we want to make a case against customization. Not because we don’t want to support our users. But because we believe there’s a better, more sustainable, and ultimately more empowering alternative: flexibility by design.
Let’s be honest: customization is seductive.
It wins deals. It makes people feel special. It says, “You matter enough that we’re willing to change everything for you.”
But what starts as an innocent change—an extra field, a unique flow, a special integration—quickly becomes something else. It becomes a dependency. And dependencies in software are not free. They have to be documented, supported, tested, versioned, maintained, migrated, debugged, and eventually deprecated.
Over time, the product team stops building forward and starts building sideways. Instead of improving the core for everyone, they’re stuck maintaining branches of logic that only exist to satisfy specific cases. Instead of focusing on quality, performance, or innovation, they’re chasing down inconsistencies introduced by a patchwork of exceptions. Bugs increase. Release cycles slow down. Confidence erodes. And worst of all, each new customer learns to expect that they too can ask for “just one more thing.”
The problem isn’t that people ask. The problem is that we say yes.
The real cost of customization isn’t just time or effort. It’s systemic.
First, there’s the cost of fragmentation. When each customer operates on a slightly different setup, it becomes increasingly difficult to ensure consistency across the product. Test coverage becomes scattered. Regression bugs creep in where no one expected them. QA becomes a guessing game—“Which version are we testing today?” And worst of all, when a critical bug does appear, solving it becomes a process of untangling who has what and why.
Second, there’s the cost of support debt. Every unique setup becomes a knowledge silo. Support teams now need a matrix of documentation to troubleshoot what should be a shared experience. The ability to say “This is how it works” disappears. Replaced instead by “It depends…”
Third, there’s the cost of technical inertia. As exceptions pile up, making improvements becomes riskier and slower. Any change to core functionality has to be checked against dozens of variants. New ideas stall because no one wants to break a workaround introduced two years ago for one specific client. Innovation dies not from lack of creativity, but from fear of disruption.
Finally, there’s the psychological cost. When you customize endlessly, your team slowly loses the sense that the product is theirs. Ownership becomes diluted. Identity becomes unclear. Instead of building something they believe in, they’re building something they’re asked to. And if everything can be changed, then nothing really means anything anymore.
These costs rarely show up on a balance sheet. But they show up in ways that matter more: in team morale, product stability, user trust, and long-term momentum.
Flexibility is not the same as customization. It’s not about saying yes to every request. It’s about designing a system that can adapt to real-world needs without losing its shape.
A flexible system is one that has options. It allows configuration. It supports toggles. It provides well-defined ways to extend, adjust, and personalize—within boundaries. It recognizes that not every hospital, company, or user works the same way, but instead of creating bespoke paths for each, it creates structured pathways for change.
The difference is profound. Customization is reactive. Flexibility is proactive.
With flexibility, we build with intent. We create rules, not exceptions. We design modules, not hacks. We allow change, but we define its scope. In doing so, we build trust—not just with our customers, but within our own teams. Everyone knows what is supported, what is configurable, and what is not. That clarity creates velocity. It empowers users without burdening the system.
In practical terms, flexibility might look like:
Role-based permission systems that adapt to organizational structure
Configurable workflows that can be rearranged without code changes
Report builders that let users define their own metrics and layouts
Theming options that allow for brand alignment without UI fragmentation
Modular components that can be turned on or off depending on need
These are not just features. They are signs of respect. They say, “We understand that you’re different—and we’ve designed for it.”
But here’s the key: the difference is designed, not improvised.
We choose flexibility not because it’s easier—it often takes more thought, more effort, and more design upfront. But we choose it because it is sustainable, scalable, and generous.
Sustainable, because it allows our systems to evolve without collapsing under the weight of their own exceptions. Scalable, because it lets us serve many without fracturing the product into a thousand versions. Generous, because it gives our users what they need without giving up what we believe in.
We want to build platforms, not projects. Platforms that can grow, adapt, and endure. Platforms where every new feature strengthens the whole, rather than carving out a new branch. Platforms that carry forward a vision, not just a to-do list.
So no, we won’t customize just for you. But yes, we will keep listening. Yes, we will keep evolving. Yes, we will build better options, smarter defaults, and more meaningful controls.
Because our goal isn’t to make software that feels tailor-made. Our goal is to make software that fits beautifully, without breaking.
That’s the real power of flexibility. And that’s the future we’re building toward.
Your job isn’t just to ship features—it’s to protect the integrity of what you ship.You are not just building for today’s use cases but for tomorrow’s scale, for unseen edge cases, and for the people who will inherit your code, your roadmap, and your decisions long after you leave.
So the next time someone asks for “just a small customization,” pause.
And ask: Does this make the system better for everyone? Or are we just buying short-term comfort at the cost of long-term resilience?
Build with care. Build with discipline. Build to last.
Great products don’t come from saying yes to everything. They come from strong opinions, clear beliefs, and the courage to build for someone—not everyone. This piece explores why being opinionated is not arrogance, but leadership—and how vision, love, and care are the most radical product features of all. If you’re building something meaningful, this is your invitation to do it on your own terms.
Piyorot Piyachan14 August 2025
In product development, it’s tempting to please everyone. To say yes. To adapt endlessly. To follow what the market says it wants. But the best products—the ones that shape industries, uplift people, and move societies forward—are rarely built that way.
They are built with vision.
They are built with love.
They are built with care.
The world doesn’t need more features. It needs more courage. More clarity. And more product teams willing to say: We see a better way.
It’s easy to fall into the rhythm of saying yes. Yes to every request. Yes to what the market expects. Yes to whatever helps close the next deal.
But the most meaningful products aren’t built by companies that say yes to everything. They’re built by teams that stand for something.
They’re built by opinionated builders—people with a clear point of view, a strong sense of purpose, and the courage to say no when it matters most.
Opinionated doesn’t mean arrogant. It means deliberate. It means designing with conviction, guided by a deeper understanding of who you’re building for, and why.
When you build a product without a strong point of view, you may get early traction. But over time, you risk becoming shapeless—drifting wherever the next big customer or competitor takes you.
Being opinionated means starting with a set of deeply held beliefs. It means saying no—even when it costs you revenue. It means resisting the urge to build for everyone, so you can build better for someone.
For us, those beliefs are clear:
We believe in platforms, not just products. We don’t ship quick fixes. We build infrastructure for long-term transformation.
We design for the lowest-paid staff, not just executives. Frontliners are at the center of our UX. Everyone else adapts.
We anticipate needs, not just respond to them. If a customer hasn’t asked for something we know they’ll need, we build it anyway.
We believe in education, not persuasion. Every customer meeting is a chance to teach, share, and reframe.
We market by permission. No tricks, no urgency, no spam. Just value, offered with respect.
We prioritize the boring stuff. Stability, security, performance. Invisible things that become painfully visible when neglected. We don’t chase shiny until the foundation is right.
We choose elegance over control. We don’t micromanage users or lock them into rigid workflows. We create clear, flexible systems that respect people’s judgment and intelligence.
We believe the best UX respects time, not just attention. We don’t celebrate engagement for its own sake. We want users to get in, do what matters, and move on with their day.
We build for clarity, not complexity. Complexity might make you feel smart. Clarity makes others feel seen, capable, and confident. We choose the latter.
We believe product is culture. Every setting, every error message, every default is a choice. A signal. A reflection of what we believe—and who we believe in.
To some, this may sound rigid or even arrogant. But in truth, this way of building comes from love—for the people we serve, the industries we care about, and the futures we want to make real.
Love, in product, means choosing who you want to fight for. And care means crafting every detail like it matters—because it does.
When you know exactly who you’re building for, you’re able to say no with compassion, yes with intention, and always with clarity.
And here’s something else most people don’t talk about: Being opinionated will teach you how to be comfortable with rejection.
Not everyone will agree with your choices. Not every customer will want what you’ve built. Not every pitch will land.
But instead of shrinking, you begin to see rejection as a filter—not a failure. You stop chasing everyone, and start attracting the right ones. The ones who believe what you believe.
And that changes you. Over time, you become confident not because everyone says yes—but because you learn to stand by what you’ve chosen, and why. You no longer define your value by applause. You define it by alignment.
This is how real confidence is built. Not from pleasing everyone. But from knowing yourself—and being brave enough to show up that way anyway.
Being opinionated isn’t just a product strategy. It’s a practice in becoming someone who can lead with conviction and love. Someone who can walk away from easy wins, so they can build something that truly lasts.
Great products aren’t just fast or beautiful. They’re respectful. Considerate. Grounded in reality, but shaped by belief. That’s why building with care is radical—it forces you to think beyond features and into consequences.
Will this help the right person?
Will this empower, not burden?
Will this bring dignity to the user?
Care is not fluff. It’s not softness. It’s precision. It’s presence. It’s leadership.
Because care is contiguous—it travels through every layer of your product, and people feel it, especially the ones you built it for.
Care shows up in a thoughtful default. In an error message that doesn’t blame. In a screen that’s not just functional but calming. It’s noticed by the right people—the ones who often go unnoticed themselves.
In a world chasing growth, speed, and efficiency, caring feels radical. But it’s not radical for the sake of standing out. It’s radical because it refuses to look away. It pays attention to what truly matters.
And here’s the thing: caring is the most fundamental trait of great leaders. Not charisma. Not decisiveness. Care.
As a product person, you are not just shaping screens—you are shaping systems, behaviors, and experiences. Whether you like it or not, that’s a position of influence. And influence demands responsibility.
That’s why building with care isn’t optional. It’s the job. It’s how you lead—quietly, consistently, and with conviction.
Not through slogans or speed—but through intentional decisions made again and again in favor of the user, not your ego.
This approach isn’t fast. It’s not always profitable at first. And it’s certainly not for everyone.
But if you believe in meaningful change—if you want to lead, not follow—then being opinionated is a necessity, not a liability. Define your “us.” Stick with it. Build on your own terms.
Because in the long run, the world doesn’t need more features. It needs more courage. More clarity. And more product teams willing to say:
We see a better way. Come with us.
Most people chase money, titles, and status—things that look like success but feel empty over time. This is a story about choosing meaning instead. About staying small, trusting young people, walking away from big deals—and remembering the moments that made it all worth it.
Piyorot Piyachan7 August 2025
Most people don’t need to be told what to want. The world already gave them a list.
Money. Fame. Rank. Power. Status. Stability.
They chase them. Then they guard them. Then they expand them. And on paper, it works. Promotions get posted. Revenue charts go up. LinkedIn gets updated. Parents feel proud.
But if you pause—just for a moment—and look closely, you’ll see something strange.
They’re all the same.
Money is money everywhere. One baht is one baht. Yours equals mine. Status? It doesn’t matter where you earned it—it fits in the same box. Power, too. Transferable. Quantifiable. Replicable. These things are commodities.
And that’s the problem.
Because in the end, success is forgettable—but stories are not.
Because if what you value is a commodity, then your journey becomes just another version of the same old story. Different face. Same plot.
I didn’t realize this at first. Like many others, I started by optimizing for what made sense. Build the thing. Launch the thing. Grow the thing. Measure the results. Improve the metrics. Repeat. It’s logical. It’s clean. It’s rewarded.
But over time, I began to feel something missing—not from the outcomes, but from the memory of the work itself.
It’s strange how that happens. You can win, and still feel nothing. And then, something shifted. Slowly at first, then all at once.
I began to notice that the moments I remembered most—personally and professionally—weren’t tied to the size of the success. They weren’t defined by numbers, or KPIs, or market reach. They were defined by something else entirely.
They were stories.
The night I stayed up with my team, not because I had to, but because we were chasing something we believed in.
The time a customer cried, not from delight, but from relief—because someone finally listened to her.
The moment we debated a single feature for hours, not because it was profitable, but because it felt right.
The path I chose to stay small, knowing it would be rough for many years to come—but also knowing it was the only way to stay true.
The decision to put trust and hope in younger generations, even when their work would take longer, and their confidence was still growing—because I saw in them the future I believed in.
The final call to walk away from a huge, prestigious opportunity—not because we couldn’t do it, but because we didn’t want to become someone we’re not.
None of those moments made it into a dashboard. But they made it into me.
That’s when I began to rewire my compass.
I stopped asking, “Will this scale?” I started asking, “Will this be a story worth telling?”
I stopped asking, “Will this impress?” I started asking, “Will this matter to someone?”
Because when you optimize for stories, everything changes.
You write differently. You lead differently. You say no more often—not out of fear, but out of clarity. You stop trying to impress everyone, and start trying to move the right ones. You stop counting everything, and start remembering what counts.
Stories are not fluff. They are architecture. They are the shape of memory.
And memory is the only thing that doesn’t convert. It doesn’t transfer. It can’t be bought. It’s yours and yours alone.
That’s why I stopped optimizing for commodities. Because I don’t want my life to be defined by what I acquired. I want it to be remembered for what I chose. What I stood for. What I built even when it didn’t make sense to anyone else but me and a few others who saw what I saw.
The best decisions I’ve ever made weren’t strategic. They were meaningful.
The best metrics I’ve ever hit didn’t show up in spreadsheets. They showed up in conversations—months or years later—when someone said,
“I still remember what you did. It changed how I see things.”
That’s when you know: the story outlived the strategy.
So no, I no longer optimize for money. I no longer optimize for scale. Not even for recognition.
I optimize for shareable stories.
Not because I want attention. But because I want to live a life worth retelling.
As AI automates the routine and generates the infinite, a new kind of work emerges—one that demands clarity, care, and direction. This essay explores the evolving role of designers in an age shaped by automation and intelligence, arguing that purpose, vision, and judgment will become the most essential tools of all. The designer is no longer just a function—but the very embodiment of the new tasks ahead.
Piyorot Piyachan31 July 2025
Automation is not new. But something about this moment—this particular wave of intelligent tools, from AI models to robotic systems—feels more permanent, more structural. Entire categories of work are being reshaped in real time. And for many, that change brings anxiety: What happens when machines can do what we once considered uniquely human? The fear is understandable. It’s not just about jobs—it’s about identity, value, contribution. But economist Daron Acemoglu offers a powerful way to reframe this tension. He suggests that technology doesn’t just displace tasks—it also creates new ones. The challenge, then, is not to cling to the past, but to recognize what emerges in the space that’s been cleared.
Beyond automation lies a new kind of work—one shaped by imagination, not instruction.
When old routines are taken over by automation, the remaining work often becomes more complex, more fluid, and more human. The repetitive tasks are the easiest to replicate. What’s left behind are the decisions, the judgments, the designs. The world doesn’t stop needing people—it starts needing different kinds of people. It needs people who can see what’s not yet built and make it real. People who can make sense of ambiguity. People who choose not just to do work, but to redefine it. That’s where the designer comes in.
In Acemoglu’s framing, technological change always carries two faces. On one side, it automates, compresses, and accelerates. On the other, it opens up space for task creation—new responsibilities that didn’t exist before. But these new tasks don’t come with instructions. They aren’t pre-defined. They’re emergent, contextual, and often messy. They require problem framing, not just problem solving. They demand a higher order of judgment, flexibility, and care.
Unlike traditional tasks that could be standardized and codified, new tasks are often born in the gray areas. They require people to ask better questions, not just give faster answers. They evolve in response to feedback, real-world complexity, and human nuance. And while AI may continue to scale, it rarely decides what should matter. That’s left to us—to the people who still carry responsibility for outcomes, meaning, and direction. This is why the designer’s mindset is so critical in the years ahead. The future may be filled with tools, but only designers will know what to do with them.
The word “designer” is often misunderstood—reduced to roles that feel niche or aesthetic. But in this era, design is not about visuals. It’s about agency. To design is to care enough to shape. It means stepping beyond what’s given and imagining what’s possible. Designers don’t accept defaults. They question them. They don’t just react to systems—they rethink them. And in a world flooded with generative output, this kind of intentionality has never been more valuable.
Designers bring agency back into environments that have become mechanized and passive. They resist the pull toward blind optimization by asking deeper questions: What is this for? Who is this serving? What is missing from the equation? They practice design not as a job function, but as a mode of seeing—one that notices when something feels off, and acts to make it better. In that sense, designers are not optional. They are essential to any future worth building.
To understand the importance of the designer in today’s context, we need to look at the full spectrum of design—not just the visible titles, but the deeper responsibilities they carry.
Product Designer
Product designers today don’t simply arrange interfaces. In the AI age, they must curate complexity. When a tool can generate a hundred options instantly, the product designer’s role becomes one of framing, editing, and applying judgment. They must make sense of abundance—choosing what to elevate, what to hide, and how to guide users through a system that thinks for itself. Their craft now lies in restraint, in narrative, in clarity. They’re not just designing screens. They’re designing relationships between users and emerging intelligences.
Business Designer
Business designers carry a different burden. As automation drives down costs and makes efficiency abundant, the question shifts: what is still worth doing? Business designers must rethink not only how a company makes money, but how it creates meaning. They interrogate assumptions about value, relevance, differentiation, and sustainability. They’re the ones who realize that just because a task can be done doesn’t mean it should be done. Their job is not to chase margins—it’s to create coherence between purpose and strategy.
System Designer
System designers operate at the connective layer, defining how people, tools, and processes interact. But in this new age, efficiency is no longer the sole goal. The real challenge is designing systems that can adapt. Systems that respect edge cases. Systems that flex without breaking. A good system designer doesn’t just optimize the workflow—they anticipate what happens when the unexpected arrives. They see the system not as a rigid structure, but as a living organism in need of care, tuning, and thoughtful evolution.
Process Designer
Process designers might work in the background, but they often shape the frontline experience. Their attention to flow, timing, handoffs, and failure points becomes even more critical when automation is involved. Because once you remove friction, you sometimes remove important checkpoints. Process designers ensure that the human experience remains intact—even as the system becomes more streamlined. They ask where humans add value, and they redesign around those moments of judgment, empathy, and decision-making.
Category Designer
And then there are category designers—the ones who don’t just improve what exists but invent entirely new ways of thinking. They see the market through a different lens. They’re not just solving problems—they’re naming them. They create new frames, new language, and new expectations. In a landscape disrupted by AI, category designers are the ones who ask, “What problem are we really solving now?” They don’t just build the solution. They define the arena in which it matters.
Each of these designer roles reflects a different part of the ecosystem. But they are united by one trait: they choose to shape, not follow.
The future will not be determined by those who can do the most tasks. It will be led by those who can ask the right questions when all the obvious tasks have already been done. AI will automate execution. But it cannot automate intention. It cannot decide what to prioritize, who to serve, how to weigh trade-offs, or how to design for people instead of metrics. That responsibility—and that privilege—remains ours.
Designers are the ones who will step into the blank space left behind by automation and say, “Let’s build something better here.” They won’t wait to be told what’s next. They’ll define what’s next. In doing so, they won’t resist the machines. They’ll redesign the context in which the machines operate.
This is not the end of work. It’s the beginning of a new relationship with it. And that relationship needs designers—not to decorate the future, but to direct it.
As we look ahead to a world shaped by intelligent systems, one truth becomes increasingly clear: the most important traits of future designers will not be technical. They will be moral, directional, and human. At the core of every meaningful act of design lies a triad of qualities that no machine can yet replicate: Purpose, Vision, and Judgment.
Without purpose, we don’t know what questions to ask. We may have data, but we won’t know which problems are worth solving. Without vision, we don’t know what to build. We may generate options, but we won’t know which path leads somewhere truly better. And without judgment, we can’t choose wisely between trade-offs. We may simulate outcomes, but we won’t know what’s right, fair, or enough.
This is where AI meets its limit. It can offer us a sea of content—charts, summaries, comparisons, even prototypes. It can generate variations, detect anomalies, optimize processes. But it does all this without intent. It does not care. It does not hope. It does not ask why something matters, or for whom. It has no stake in the outcome. It has no agency.
Only humans carry that weight. And among humans, it’s the designers—those who choose to think deliberately about change—who must carry it first.
To be a great designer in the age of AI is not to compete with the machine. It is to direct it. To be the one who decides what is worth building, what is worth ignoring, what is worth protecting. Designers must make the final call—not because they know everything, but because they carry something the model cannot: responsibility. They are the ones who say yes or no. Who choose to proceed or pause. Who understands that sometimes the most important design move is not to act.
In that sense, the designer is not being left behind in this era. They are being called to rise—to own the judgment that machines cannot hold. To bring purpose where there is only productivity. To bring vision where there is only variance. And to lead not with certainty, but with care.
The tools will only get better. But so must we.
In the end, the new tasks aren’t just things we do—they’re roles we grow into. And perhaps no role captures that shift more fully than the designer. Designers are not only responding to change; they are becoming the very embodiment of it. In many ways, designers are both the old task and the new. Not because their methods remain the same—but because their responsibility deepens. The questions are harder now. The stakes are higher. The terrain, more complex. But the heart of the work remains: to imagine better ways forward—and to bring them to life.
The designers we need today are not just creatives or strategists. They are systems thinkers who understand the technology, the context, the culture. They read signals from society as fluently as they do interface flows or policy documents. They are just as comfortable navigating emerging AI models as they are sitting with a user who feels overlooked. They do not simply draw solutions—they define the destination. With clarity, care, and courage.
What makes a designer irreplaceable in the age of AI is not what they make, but what they choose to make matter. They don’t chase every possibility. They don’t automate for the sake of efficiency. They hold space for intention. For meaning. For the long view.
The new tasks are already here. They don’t look like step-by-step instructions. They look like questions, tensions, challenges without easy answers. And in every one of them, a designer is waiting—not just to solve the problem, but to shape the future that problem belongs to.
What happens when AI takes over the tasks once reserved for junior analysts? In this conversation between a mentor and their interns, we explore how to start a real career in data science when the easy work is gone. Through skill maps, career tracks, and reflections on what AI still can’t do, this is a guide for those who want to thrive by choosing hard, meaningful problems—and learning to connect data with context.
Piyorot Piyachan24 July 2025
When I sit down with new interns or junior hires on our data team, I no longer begin by explaining what we do at Mutrack or what tools we use. I start with a quiet truth: the career path you thought you were on might not exist anymore.
It’s not your fault. Most universities still teach data analysis like it’s 2015. They hand you Python, R, some linear regression, a few business cases, and a capstone project that ends with a dashboard. But that path—the one that starts with cleaning data, writing queries, building reports, and slowly moving up to machine learning and strategic work—has already been flattened by artificial intelligence. Entry-level jobs, as we knew them, are disappearing. AI now handles a large portion of what junior analysts used to do. What we called “easy tasks”—routine querying, basic modeling, and even interpreting simple trends—are increasingly managed by tools that require no analyst at all.
That’s why I believe every aspiring data professional needs to confront a hard question early: If AI can do what I thought I was going to do, then what should I be preparing for?
In the age of artificial intelligence, data is no longer just information—it’s intuition made visible. What you see here isn’t just form, it’s pattern, uncertainty, possibility.
This isn’t a crisis. It’s a call to clarity. There is still incredible demand for data talent. But that demand has shifted. We no longer need people who can run reports. We need people who can frame problems, challenge assumptions, and translate messy operational questions into structured insights. We need people who understand both the business and the data. And above all, we need people who know how to work on what MIT economist Daron Acemoglu calls “hard tasks”—the contextual, strategic, high-ambiguity work that AI still struggles with. The easy stuff is gone. The hard stuff is where you must begin.
When I talk to my interns about this, I usually pull out a chart—a skill map I built for our data analysts and scientists at Mutrack. It’s not a checklist. It’s a map of possibilities. Across this map are the real competencies we rely on in our product and operations: industry knowledge, market research, product thinking, statistics, machine learning, web development, DevOps, data pipelines, presentation skills, and more. No one masters them all. But everyone must pick a corner and go deep.
Seven areas, thirty skills. No one masters them all, but everyone must pick a corner and go deep.
This is our skill map for data professionals in the AI era—built not as a checklist, but as a compass. No one masters it all. But everyone must choose a direction, go deep, and make it matter.
We start with Industry Knowledge. This isn’t just knowing what the business does. It’s about immersing yourself in the ecosystem. In our case, that means hospitals. How does a patient journey unfold from arrival to discharge? What bottlenecks frustrate staff and delay care? What unspoken trade-offs do hospital administrators make every day? Without this context, your data work is untethered—like diagnosing a patient without understanding the hospital they’re in.
Then there’s Market Research. This is your radar. It’s your ability to look outside the walls of your own data warehouse and understand what’s happening in the industry. What trends are emerging? What competitors are moving faster? What macro shifts—like policy or technology—might affect decision-making? Good analysts aren’t just number crunchers. They’re context seekers.
Product Design and Development follows. At first glance, this doesn’t look like a data skill. But if your insight doesn’t lead to action, what was it for? Understanding product design means understanding constraints. What makes a product usable? What makes a feature stick? If your chart can inform a better design, or your model can support a new feature, you’re no longer a back-office analyst—you’re a builder.
Now we move to the technical middle of the map. Programming is your toolset. It’s how you automate, build, test, and scale your ideas. It’s not about how fancy your code is—it’s about how effective and repeatable your solutions are. If you know how to code, you know how to ship.
Statistics is where your judgment begins. You need more than averages. You need to understand distributions, biases, confounding variables, and causality. Statistical thinking lets you question your own output. It keeps you honest.
From there we expand to Machine Learning. It’s not about fitting neural networks for the sake of it. It’s about when to use learning systems, how to evaluate models, and when to say, “We don’t need AI—we need a simple rule.” Machine learning is powerful, but restraint is just as important.
Data Preparation is the unglamorous heart of analysis. Every dataset tells a different story depending on how it’s cleaned, filtered, and shaped. Knowing how to wrangle messy data is still essential. It’s your first signal of whether the work ahead is meaningful or misleading.
Modeling is about translating questions into structured forms. It’s about building abstractions, testing them, and refining them over time. Whether you’re forecasting, segmenting, or running simulations, modeling is how you make ideas concrete.
Data Visualization is how you guide attention. It’s how you say, “Look here. This is what matters.” Great data people don’t make pretty charts. They design conversations. They help others see what they see.
Further into systems, we arrive at DevOps and Database Management. These are often overlooked by analysts but essential for anyone working in production environments. If you want your insight to live inside a system that runs every day, you must understand infrastructure. How do we deploy updates? Where does the data live? What happens when it grows 10x?
Big Data Infrastructure extends this further. When you go from thousands to millions of rows, or when data comes from real-time sources like sensors or applications, you must know how to scale. Big data isn’t about volume—it’s about design decisions.
Data Streaming and Pipelines follow. This is about movement—how data flows from one place to another in real time. If your system relies on up-to-the-second information, like our dispatch engine for hospital porters, then building reliable, monitored, fault-tolerant pipelines is not just nice to have—it’s life-critical.
CI/CD, or Continuous Integration and Deployment, brings discipline to all of this. It’s how we test, verify, and release improvements with confidence. It’s also how we prevent breaking everything when we’re just trying to fix one thing. Analysts who understand CI/CD can participate in engineering conversations—and ship faster.
Last but never least, Presentation and Storytelling. This is the multiplier. It’s not about sounding smart. It’s about making others smarter. When you can tell the story behind the data—what matters, what changed, what we should do next—you become irreplaceable. Data becomes strategy.
After we cover the map, we step back. It’s too much to master all at once. So I offer a simpler lens: What kind of data person do you want to become?
At Mutrack, we describe three archetypes: Product-Focused, Data-Focused, and Ops-Focused. Each is a legitimate, defensible path. Each creates real value. And more importantly, each comes with its own rhythm of work, source of fulfillment, and path toward mastery. Let me walk you through what each track truly looks and feels like when you live it for real.
If you’re Product-Focused, you live in the intersection of customer insight, product evolution, and data interpretation. You don’t wait for a Jira ticket. You initiate conversations. You ask, “Why are we building this? What’s the real need?”
You might find yourself sitting with a nurse during a hospital visit, watching how they juggle screens, forms, and patient needs, just to discover a 3-second friction that no metric captured. You are part analyst, part UX whisperer, part mini-PM. You love figuring out not just what’s broken—but what’s missing. You use data as your compass, not just your evidence. Your presentations change roadmaps. Your questions shape features.
You are trusted not because you have all the answers, but because you ask the most clarifying ones. Over time, you become the person people turn to when they want to build things that actually matter.
If you’re Data-Focused, you go deep. You’re the kind of person who loses track of time trying to answer, “Why is this pattern showing up?” You build models not for show, but to test, learn, and iterate. You’re skeptical of assumptions—even your own.
You enjoy the elegance of a well-written function and the intellectual challenge of a multivariate A/B test. You obsess over statistical rigor. You care about cleaning the data as much as analyzing it. And yet, you’re not trapped in theory. You want your work to influence decisions, shape strategy, and unlock value. In your hands, a messy dataset becomes a story, a prototype, a lever. You learn to zoom in with precision and zoom out with wisdom.
People may not always understand your equations—but they understand the clarity your work brings. That’s your power.
If you’re Ops-Focused, you are the engineer behind the curtain. You take pride in making complex systems look simple on the outside. You love when a job dispatch gets sent to the right person in the right place without anyone noticing the orchestration underneath.
You think about latency, failovers, monitoring, and scale—not because it’s glamorous, but because it’s the kind of work that must be done right the first time. You work with databases, pipelines, deployment pipelines, and edge cases. You thrive in real-time environments. When systems go down, you’re the one people call. But more importantly, when things run smoothly, it’s because of you.
You find elegance in efficiency, strength in reliability, and pride in being invisible but essential. You might not be center stage, but you’re the one holding the rigging ropes so everyone else can perform. And in your quiet mastery, you create the conditions for everything else to thrive.
Each track has its beauty. But what unites them all is a shared truth: in this new world, your career starts not with easy tasks, but with meaningful ones. You must choose hard problems early. You must get used to ambiguity. You must learn to lead, not just execute.
When people say “data is the new oil,” they forget that oil has no value unless it’s refined, transported, and used. The same is true for data. We don’t need people who just extract it. We need people who make it matter.
So if you’re about to work in the data-rich world, here’s my advice: Don’t look for the ladder. It’s gone. Look for a wall worth climbing. Choose your grip carefully. And pull others up with you.
And if we circle back to where we started—to Daron Acemoglu’s argument about easy and hard tasks—the lesson becomes clearer. In the age of AI, it’s no longer enough to master one discipline. Knowing how to write code or fit models won’t protect you. The tasks that survive—those hard, ambiguous, deeply human tasks—demand more than skill. They demand awareness.
In this increasingly complex world, filled with data streams and soon, super-intelligent agents, it is still possible for humans—just like you and me—to not only survive, but to thrive. Not because we process faster, or calculate better. But because we understand people. Because we see nuance. Because we recognize contradiction and possibility where AI sees only patterns. We bring context. We bring judgment. We bring purpose.
The real work now is connecting the invisible dots—across teams, across tools, across silos. And we do that through our own lens, shaped by experience, empathy, and conviction. That is what makes a great data professional today.
So choose your track. Pick a hard problem. Embrace complexity. Stay close to reality. Keep asking questions. And above all, don’t forget the human behind the data. That’s where the future still belongs to us.
Everyone says design thinking starts with the user. But what if it starts with you? What if the best innovations don’t follow a method, but a conviction? This piece explores the heart of design thinking—not as a fixed process, but as a mindset that begins wherever belief, empathy, and intent collide.
Piyorot Piyachan17 July 2025
I asked a few experts what Design Thinking really means. The answers I received came back circling a similar definition:
From ChatGPT – 12:02, July 11, 2025
Design Thinking is a design-oriented thought process that emphasizes deeply understanding problems from the user’s perspective, then using that understanding to create solutions that genuinely address those problems. Its key characteristics include iteration, hands-on prototyping, user testing, and learning from mistakes in order to continuously improve the solution.
From Gemini – 12:05, July 11, 2025
Design Thinking is a problem-solving and innovation process that centers around the user or consumer. It emphasizes a deep understanding of the user’s true needs and problems in order to generate ideas and solutions that are truly effective.
From Claude – 12:09, July 11, 2025
Design Thinking is a human-centered problem-solving process that focuses on deeply understanding the needs of users and leads to the creation of innovations or solutions that respond to those needs.
From Perplexity – 12:11, July 11, 2025
Design Thinking, or thinking through design, is a process of thinking and problem-solving that centers on understanding human or user needs (Human-Centered Design), with the goal of creating innovations and solutions that meet those needs effectively and tangibly.
The answers all clearly share common themes: design-oriented thinking, user-centered focus, deep understanding of the problem, and innovation.
Seeing this, can we then conclude that “Design Thinking is a problem-solving process that starts with understanding users and leads to new solutions that truly address the need”? Can we say that “if we begin by understanding any problem, we are already stepping into the path of Design Thinking”? And can we say that “putting the user at the center is the starting point of innovation through Design Thinking”?
For me, the answer is no—because the truest form of Design Thinking starts from within ourselves.
Yes—before we even say we are doing Design Thinking, we must ask the question: who are we designing for, and why? Because if we don’t know who we’re creating for, we may end up building something that looks great, is packed with features, and technically works—but means absolutely nothing to anyone. So when we say “start with the user,” it’s not just a cool phrase to put on a slide or scribble on a whiteboard during workshops. It means we must literally step into the lives of the people we are designing for. We must listen, observe, watch, and feel what problems they face in their daily lives—and understand how they’ve tried to deal with them on their own.
There is no Design Thinking lesson that doesn’t include the word empathy. And I’m no exception. Every time I think about solving a problem, that word is something I try to keep front and center.
In the world of Design Thinking, when people mention empathy, they often think of understanding emotions, contexts, or user-stated needs—and that’s not wrong. But to me, empathy doesn’t always mean giving users what they ask for—it means choosing to solve what truly matters first. Deciding to tackle the real problem is a deeper form of empathy. Good design doesn’t mean doing everything the user says—it’s about using your judgment as the one responsible for creating, to decide what to believe, who to trust, and what kind of solution will actually be most helpful.
Starting from the user helps us understand the problem more deeply. Meeting with people, having conversations, and experiencing their real environment makes it easier to develop true empathy. But what if we don’t get a chance to meet real users? What if we can’t observe them on-site or study their behavior directly?
Does that mean we’ve lost our chance to apply Design Thinking? The answer is no, because…
Yes—starting with the user is important. But many times, the thing we have to rely on the most isn’t the user’s voice, but our own. Because when we don’t get the chance to meet real users, when the data is insufficient, when we don’t have enough time to sit with the problem, or when no one tells us what they’re going through—the only thing we’re left with is our instinct, our beliefs, our experiences, and our own intentions.
In the real world, Design Thinking rarely begins in a research field full of insights. It often starts in a quiet room, with just us and a few unanswered questions. In those moments, Design Thinking doesn’t mean waiting until all the data is in—it means using ourselves as the starting point of understanding. Because if we’ve ever faced the same problem, if we’ve ever felt what the users feel, or if we have enough imagination to step into someone else’s life—that’s already enough to start designing something that matters.
I believe great ideas don’t just come from looking outward. They come from having the courage to ask ourselves honestly, “If I were them, how would I feel?” and “If it were me, how much better would I want this to be?” The best designers aren’t just the ones who understand users. They’re the ones who act on their conviction that something should be better—even if no one asked for it yet.
Of course, there’s risk in this path. Designing too much from within can trap us in our own perspective. We can get lost. But tell me—what innovation in human history didn’t start with risk? None. And if we believe we’re building innovation, the sooner we’re willing to take risks, the sooner we’ll learn and get closer to breakthrough.
Because ultimately, the truth is: no one is coming on a white horse to save us. When we face a dead end, when creativity dries up, when we lose confidence in our design ideas—going back to users and hoping they’ll light the way is often wishful thinking. No one can save us. There is only us. Only the intention that comes from within. And only the resolve and the story we repeat to ourselves will keep us from giving up too soon.
Design Thinking is us, not someone else. Design Thinking is our mission, and ours alone.
This is a fascinating point—who exactly is responsible for Design Thinking in a team? Let’s ask the experts one more time.
From ChatGPT – 13:49, July 11, 2025
In a traditional software development team, the people who usually take direct responsibility for Design Thinking are UX/UI designers or product designers. Their role is to shape the user experience, and they typically possess the core skills associated with Design Thinking: user research, problem understanding, prototyping, and user testing.
That said, another key role is the Product Manager (PM). A PM defines what the problem is, what should be solved, and when. If a PM sees beyond roadmaps and backlogs and genuinely seeks to understand users, they can drive Design Thinking alongside designers in a very powerful way.
In great teams, developers or engineers are also involved—not necessarily as the lead thinkers, but as co-creators who contribute by shaping what’s technically possible. They can offer creative, elegant solutions—especially when involved early on during the user research or ideation phases.
What do I think of this answer? It makes things very clear: Design Thinking is a collaborative effort. No matter what role we play, if we care about this way of working, we need the knowledge, perspectives, and contributions of others. Different viewpoints, varied life experiences, and diverse convictions from teammates help us see things we’ve never noticed, hear things we never imagined, and most importantly—ask bigger, better questions.
All of this leads to undeniably good outcomes. After all, no one in the world is smarter than ten people sitting at the same table. Everyone knows something others don’t. Everyone’s lived through something others haven’t. Everyone sees some corner of the truth that others can’t quite grasp.
That’s why great design almost never happens in isolation. Professional design teams are often made up of people with different backgrounds, experiences, and ways of thinking. It’s that diversity that lets us discover what we’ve never seen before—and ask the kind of questions we never dared to ask.
But does that mean Design Thinking is only a group activity? The answer is—no. Because…
It is our responsibility—and ours alone. Why do I believe this?
Because if we simply ask ourselves, “What would I have left if no one else on the team cared about this?”—would we just let things slide? Let the process of thinking, designing, and decision-making happen and dissolve on its own?
If we truly care about this, the answer should always be no. And that, in itself, is the clearest proof that says:
“I don’t need anyone else—not even one person—because this begins and ends with me alone.”
If we believe that Design Thinking means deeply understanding design, then where do we stand now? Do we understand it only on the surface level—just enough to use it? Just the look and feel of the interface? If we go deeper and find ourselves lost, uninterested, or reliant on others, should that worry us?
When we present our design, how deeply can we explain it? If we say Design Thinking is about understanding how things work, can we really guide the team, lead the direction, and set the standards?
For those truly committed to this way of thinking, Design Thinking whispers:“You must know and understand as much as possible—to the point you no longer need anyone else while thinking.”
When we draw a single button on an app screen, is that all we care about? Its size, color, shape, border radius, and font? Or do we also understand when this button should be active, why it should or shouldn’t be pressed, who will press it, and under what circumstances pressing it holds meaning?
Do we see the deeper structure of the system that supports what we design? Can we trace the impact of this tiny change across other systems? How well can we explain our decisions to others? Do we feel truly confident that this is the best solution we can come up with at this moment?
Or are we still designing just the front layer, waiting for others to take responsibility for the deeper dimensions? Are we just following routines passed down over time? Or are we simply executing orders—orders with no solid reasoning behind them?
Do we panic when there’s no one to ask? Can we trust our own thinking when no one is there to validate it? Are we ready to think alone—without waiting for someone else to set our priorities?
Are we willing to defend this design idea with all our strength, knowledge, and vision? Do we truly want to elevate our work to that level?
Because Design Thinking has never been about the majority. It has always been about us alone from the beginning. And if we want to be designers who work to the standards this discipline deserves, we must always start by being brave enough to think—and to build—on our own.
When I revisit the definitions “What is design thinking?” again, the message is crystal clear from the very first sentence—Design Thinking is user-centered. That alone says everything. We are trying to design for others, solve problems for others, build something for others.
No textbook ever recommends that we forget the user, ignore reality, or reject external input. And it’s exactly this mindset that has allowed us to experience countless great products and services that make us feel genuinely cared for in today’s world.
One example that always comes to my mind when I think about “designing for others” is Airbnb in its early days. The challenge wasn’t just about building an online platform for renting homes—it was far more complex: nobody trusted anyone.
Imagine letting a stranger sleep in your home. Now imagine being that stranger, walking into someone’s home halfway across the world. What Airbnb needed to build wasn’t just a slick website that made booking easy. They had to design a feeling of safety—something nobody could quite articulate or request, yet everyone needed to feel.
Airbnb called this principle Design for Trust.
They experimented with tiny details: using profile photos, displaying real names, writing honest-sounding reviews, allowing hosts to answer questions, and even styling their UI to feel warm rather than sharp like most tech platforms. None of this was designed to look pretty—it was designed to help two complete strangers trust each other just enough to hit the “book” button or hand over their house keys.
When we start with others in mind, we set aside our ego. We stop insisting that our designs must be right. When we accept that their problems are our responsibility, we stop blaming the user. We stop saying things like, “It’s not that hard; they just don’t get it,” or “I’ve explained it a hundred times—why can’t they figure it out?”
Airbnb is a masterclass—not just in design approach, but in mindset. A team designing for trust doesn’t just ask, “How do we get people to book?” They ask, “How do we make people feel safe enough to trust each other?” That’s the heart of designing for others. It doesn’t just solve visible problems—it addresses unspoken feelings no one dares to voice.
And that’s the key difference between listening to respond and understanding to act.
Because in the world of Design Thinking, solving others’ problems might be the end goal—but taking action simply because we feel that something should be better, even when no one asks, is a truth we must not ignore.
So the question is—Can Design Thinking still be considered “valid” if we admit that sometimes we don’t design to serve others, but to protect our own sense of what’s right?
If we look closely, no Airbnb user ever said to the team, “Can you help me feel safe trusting a stranger?”
Yet that became the very soul of the platform they built—quiet, but powerful. And who made the decision to create that experience? The answer: the designer themselves—only us.
No masterpiece ever emerged without deep commitment, relentless effort, and perseverance through difficulty. And this is the most overlooked definition of Design Thinking: It’s not just about responding to the needs of others. It’s about answering the deep conviction within ourselves that the world should be better—even if no one has asked for it.
Because no promise is greater than the one we make to ourselves: To do our very best—for others.
Joe Gebbia, Airbnb co-founder and its early design leader, is a perfect example of this principle. The concept of “Designing for Trust” didn’t come from user requests. It didn’t emerge from the research team. It came from him—from someone who wanted to do it, and believed it was something the world needed.
And believe it or not, the phrase “I want to do it—because I want to do it” is one of the most pure and powerful philosophies in all of Design Thinking.
Because I wanted to,
I designed a platform to help strangers trust one another. (Airbnb)
I created a text box that limits messages to 140 characters. (Twitter)
I believed the best stylus is your finger—and changed how the world uses phones. (Apple)
I crafted clothes that allowed women to breathe and move freely. (Chanel)
I built an airline that made returning home feel like a celebration in the sky. (Virgin Atlantic)
I asked the questions no one dared ask and spent decades seeking the answers alone. (Einstein)
I wrote songs to release feelings I had no other place for—and they became a safe space for millions. (Kurt Cobain – Nirvana)
I played point guard at 6’9” and rewrote the mental rules of basketball. (Magic Johnson)
Can anyone truly deny that these small ideas—born from the desire to create for oneself—didn’t change the world?
No one assigned it. No one requested it. No one wrote the brief. They just did it—because they believed it should exist.
And that is the purest form of Design Thinking: When we dare to create for ourselves, driven by a responsibility greater than our own ego.
Then, and only then, do we realize—Designing for yourself isn’t in conflict with designing for others. It’s the path to understanding others in the deepest way possible.
After writing thousands of words—exploring ideas, stories, individuals, and all sorts of beliefs surrounding Design Thinking—I started to ask myself: What is design thinking, really?
Or maybe the real question is—between “Design” and “Thinking,” which one matters more?
Or perhaps, it never truly existed in the first place.
We use the term as a way to convey some noble intention: a desire to understand others, to make things better, to use creativity to solve the world’s problems. But if you look closely, you’ll notice something strange—The people who truly changed the world never once claimed they were “designing” or “thinking.”
Apple never labeled their process as one of “empathy.”
Coco Chanel never sat down to draft a “target group matrix.”
Magic Johnson never mapped his problem space on a whiteboard.
They did what they did not because it had a name—But because they felt it should be better. And they had the courage to make it better. That, I believe, is what we should really value.
Because once you peel back all the layers of theory and technique, you’ll see that “design” is really just one of a hundred ways to build something new. And what gives it power is not the process itself, But the thought, emotion, and self we pour into it.
When design is small, but thought and individuality are big
So maybe Design Thinking isn’t really a method, a framework, or a set of tools that guarantees results. Maybe it’s just what happens when someone has an idea they’re determined to bring to life—with a deep understanding of the world outside, and an equally deep sense of purpose from within.
It’s the intention to make things better, By using your own thinking—No matter who it’s for, or what it’s for.
And perhaps. That’s what we should truly call it, when design becomes small, and thinking—and individuality—becomes everything.
Postscript: When I asked again what is design thinking?, here was the answer I got—
From ChatGPT – 18:34, July 11, 2025
Design Thinking is a creative problem-solving process that centers on the user. It emphasizes deep understanding of user needs, accurately defining the problem, generating new ideas, building prototypes, and testing solutions with real users. The goal is to discover effective, practical, and meaningful solutions that add value.
Roughly six hours passed—and the answer from the same expert had shifted slightly in detail.
Design Thinking, as a theory or formula, may not truly exist. But the thought process, the understanding, and the unwavering conviction—those are what endure.
Most people believe a good system should make life easier. But truly great systems do something more powerful: they create intentional tension — the kind that nudges users out of autopilot and into meaningful reflection, better decisions, and long-term growth. In this article, we explore how systems can challenge without overwhelming, support without overstepping, and guide users to become sharper, not just faster. A good system doesn’t just work. It makes people better.
Piyorot Piyachan10 July 2025
Because true progress often begins with doing something different. When people talk about a good system, they often imagine one that makes life easier — a system that completes tasks for you, removes complexity from every step, and eliminates the need for decisions, pauses, or uncertainty.
But in reality, the best systems don’t do everything for you. The best systems create tension — intentionally and purposefully.
It creates moments where users must stop and think. It introduces a slight discomfort — not anxiety, but a nudge — and that’s exactly where transformation begins.
It’s the moment someone realizes that the way they’ve always done things may not be the best way anymore. It pulls people out of autopilot. It invites new perspectives, different thinking, and a step forward in growth.
A good system knows what should be automated — and what should be left for the user to think through. It removes repetitive, boring, low-value work. It reduces friction where it’s unnecessary. It opens up new paths users may have never considered. And most importantly, it creates clarity — so that users can make better decisions, at a higher level.
The best systems don’t replace humans — they elevate them.
Tension doesn’t mean conflict or struggle. It means a pull that takes us out of our usual spot. It’s the force that moves us forward — even when we don’t yet know where the path will lead.
It’s the willingness to admit: “We’re not sure if the new way will work — or how it will — but we’re willing to try.”
It’s a team agreeing to change a process they’ve followed for ten years, just to explore something new.
It’s the decision to invest time, resources, and trust without a guarantee of outcome.
It’s choosing to look beyond just today — and toward next year, and the years after that.
Tension makes us think more. Try more. And most importantly — it helps us see more clearly what’s working… and what’s not.
Good tension doesn’t happen by accident. It must be designed — with intention, with empathy, and with a clear understanding of where the user is today… and where you want them to go next.
Here are five steps to design experiences and systems that create purposeful, positive tension.
The first step is to identify areas where users are on autopilot — simply going through the motions.
It might be a dashboard that’s always open but never prompts action. It might be a feature that looks good, but never sparks a new decision.
These are the moments to ask:
“Is this too easy?”
“Is this something users just glance at without it changing anything?”
Positive tension begins when we help users exit autopilot mode.
Once we know what’s too comfortable, we must define the transformation we want to encourage.
Not just knowing more — but thinking differently, making better decisions, or having the courage to try something new.
Ask yourself:
“What do we hope the user will do differently after using this feature?”
“What behavior would signal that our tension is working?”
For example: If users previously only looked at dashboards, maybe now we want them to set a new goal or investigate the cause behind a change in metrics.
That’s the kind of tension we want to support.
When we know the change we want, the next step is to design small, thoughtful interruptions — not obstacles, but gentle nudges that invite reflection.
This might be a question:
“What do you want to improve?”
“Why did this data change?”
Or it could be a constraint: For example, letting users select only three key metrics instead of showing everything — to force focus and intentionality.
The tension here doesn’t have to be big — just enough to pause and reconnect with their goals.
Tension without support leads to frustration. Our aim is not to challenge users into failure — but to help them grow.
After we create the moment of reflection, we must offer help — the right information, suggestions, or clear paths forward.
“Want to explore this number? Click for full details.”
“Want to set a goal? Start with this template.”
Positive tension should come with the right kind of scaffolding — not just a question and then silence.
Finally, remember: tension comes in degrees. Too little, and users feel nothing. Too much, and they pull away.
Good design sets the tension just right — enough to feel it, but not enough to feel lost. Enough to think — but not enough to feel abandoned.
Observe actual usage:
Are users asking better questions?
Are new behaviors emerging?
Or are they avoiding the feature altogether?
Don’t be afraid to design small points of friction — if they help users see the bigger picture, think more clearly, and make better decisions.
Tension is a gift — not an obstacle. It’s a moment that nudges users to gain clarity, think deeper, and act with more confidence.
As system designers, we’re not just building tools — we’re shaping thought. We’re redefining the relationship between people and work.
A good system isn’t one that does everything for us — it’s one that pushes us to think deeper, decide with greater clarity, and grow every time we use it.
And because of that the best systems aren’t the ones that make everything easy. They’re the ones that make everything better — through well-timed tension.
Many users will say they want a system that does everything for them: no thinking, no choices, no exceptions. But our job is to know when not to give them that.
To stop — before users lose their role. To stop — before we remove the most crucial moments of decision.
Because often, the most valuable thing a system can do isn’t to make decisions for us — but to create the space for us to decide, with clarity and confidence.
So if you’re building a system today, ask yourself:
Where does your system create positive tension?
And how does it help your users ask better questions?
Sometimes, just that shift in thinking can change everything.
Most people think a project manager keeps things on track. But in reality, the best project managers ask the hard questions before anyone else does. They don’t just manage timelines—they shape direction, challenge assumptions, and create clarity where there was none.
Piyorot Piyachan3 July 2025
The title “Project Manager” carries a sense of grandeur. A manager—someone in charge, someone knowledgeable, someone who determines the course, someone everyone depends on. But in reality, it’s not always like that.
“Project Manager” also carries a sense of isolation (because there is no one else), powerlessness (because no one works under me), lack of knowledge (in technical matters), and a duty-bound existence (because I have never once set the final deadline myself). This is the reality, every single time.
In normal settings and situations, the project manager is invisible. Why? Because in the typical definition, this person is only responsible for writing plans, following up tasks, organizing meetings, sending and replying to emails, taking notes, and handling complaints no one else wants to own. In this kind of situation, if everyone communicates well, understands each other, works together as a team, upholds standards, and behaves professionally, I should be completely invisible.
Even in 2025, this “normal situation” rarely happens. Teams don’t want to be teams. People avoid communication. And there’s always work no one wants to do. That’s why I am so desperately needed. So much so that if I’m not in the equation, nothing moves forward. If I don’t show up, there is no team. If I don’t intervene, conflicts grow. But every time I stop and reflect with honesty, I ask: Why am I here, really?
Everyone else at the table or on the Zoom call can answer this easily:
But what about me? What do I do? Where is the value I bring? Planning, following up, organizing, note-taking, and doing the things no one else wants to do? Do these activities require special skills? Are there things I can do that others can’t? Answering without bias: No.
Anyone who knows Excel can make a plan. Anyone who understands Jira can follow up in Slack. And everyone can write an email. Even the most unwanted tasks—if someone must do them, they will. Again, honestly, anyone can do this job.
So what am I doing here? In this meeting? When I look closely, I am easily replaceable—until I understand one of the most important principles:
While most believe a project manager should dive deep into every detail, draw comprehensive Gantt charts, send out 20 emails a day to coordinate 50 tasks, or respond to every chat within five minutes—that is the fastest path to becoming someone easily replaced. Deep, detailed, and instant.
But if we want to be better, to bring more value, to elevate the standard of “Project Manager,” we must do the opposite. We must learn to focus on being broad, forward-looking, and grounded.
Believe it or not, 95% of people in the team are trained to focus on depth, detail, and immediacy. The word “focus” is commonly defined to mean narrow, now, and self-oriented:
Everyone is diving into details, staring at Jira tasks, Notion boards, Excel trackers, or whatever tools they use. Everyone is deep into writing requirements, arguing over test cases, rescheduling sprints, assigning owners, moving deadlines, and reorganizing lanes.
If we, as project managers, are merely listeners, note-takers, followers, or mediators, we’re being sucked into the vortex of depth, detail, and urgency. But if we listen and then ask the kind of question that makes everyone stop talking, if we observe and then pose a question no one is prepared to answer, we are fulfilling our true role.
Because our questions are broad, long-term, and steady. They require synthesis of thoughts that people aren’t trained to do. They provoke thinking in ways teams rarely expect.
We don’t create value by knowing more. We create value by stepping back to see what others can’t. It’s a rare skill. A difficult one to master. And it requires a kind of quiet courage that’s hard to find in this day and age.
Because we see what others don’t, we earn our seat in that room. We become valued not because we know more technical details, but because we ask better questions, capture insights more clearly, and dare to challenge assumptions the team has long held without question.
“Before we talk about anything else, can someone please tell me—what is the objective of this project?”
We must ask this question every time a project kicks off. It sounds simple, direct. But in our experience, it’s the question that generates the most silence in any room. And that silence? That’s the sign we’re looking for.
Because if the team can’t answer this, then the plan has no true destination.
Picture a typical kick-off meeting. Everyone’s present: devs, QA, product manager, perhaps even an executive dropping in. Everyone expects the usual questions:
But those are not the right starting points. And that’s not the kind of project manager we want to be. So we ask again—clearly, calmly:
“What is the objective of this project?”
“Uhh… to build a new system.” “To serve a new segment of customers.” “To improve performance.” “To deliver according to the roadmap.” “Because the board wants it.”
These answers sound logical but they aren’t objectives. They are expected outcomes, or politically safe responses. Words like “improve,” “add,” or “support” lack direction, scope, and measurable anchors.
If we can easily answer when a project will end but can’t answer why it began, we are already in trouble.
Unclear objectives lead to vague scopes, competing priorities, bloated expectations, and exhausting misalignment. And when we reflect with professional honesty, we must ask: will we really let this happen and say nothing?
If our objective is unclear, we are working in the dark—no matter how solid the requirements seem or how capable the team is. The same problems always return:
That’s why we ask the question early. Not to delay, but to protect the project.
Why don’t people answer this question?
Because the real answers aren’t pretty. Sometimes it’s “because leadership said so.” Sometimes it’s “because we inherited half-baked work.” Sometimes it’s just “no one was brave enough to cancel it.”
And many times, the objective doesn’t exist yet. Because the real conversation hasn’t happened: What problem are we solving? For whom?
The danger isn’t in having no answer. The danger is pretending we do.
So we must pause everything—before timelines, sprints, phases, milestones, Jira boards, Slack channels, email threads, and weekly status meetings. We stop, not to slow things down, but to give the project a chance to go somewhere meaningful.
Because if we skip this now, we’ll revisit it again in a month. And the next. And by then, it will no longer be a question—it will be frustration, blame, and burnout.
Anyone can run a kickoff meeting. Anyone can assign tasks, write in Notion, or summarize in an email. Anyone can chase a partner or file a request.
But the harder job, the real job of a project manager, is asking the right question at the right time—the kind of question that silences a room and wakes people up.
The real job of a project manager isn’t managing tasks—it’s creating clarity, asking the right questions, and guiding the team toward a meaningful objective.
We know that objectives are rarely placed neatly on the table. They aren’t written on the first slide. They don’t sit clearly in one person’s head. They’re often scattered across half-sentences, vague comments, or hidden in silence.
That’s why we help teams uncover them—not with instructions, but with questions.
We don’t ask: “Who is doing what?” We ask: “If this project truly succeeds, what changes for the user?”
We don’t ask: “When is the release date?” We ask: “What must not be missing if we’re to call this a success?”
We don’t begin with: “How many weeks for testing?” We ask: “What if we finish the project and no one uses it—is that still a success?”
We don’t just ask: “Which sprint is this feature in?” We ask: “How does this align with our team or company’s long-term direction?”
We’re not here to answer everything, but to ask what no one else is asking. We ask not to extract answers, but to create space for shared understanding to emerge. And when someone finally says something that resonates, we catch it, shape it, clarify it—until everyone sees the same thing, clearly.
Because sometimes, the objective was there all along. Just waiting to be spoken aloud.
We’re not here just to deliver projects. We’re here to give them meaning, direction, and clarity.
In the early days of a project, we may not be the smartest or the loudest in the room. We’re not the ones who make the final decisions, write the most code, or design the best interfaces.
But what we must bring is courage. The courage to think differently. Ask differently. Act differently. And respond differently.
The courage to stay still when others want to rush. To ask when others want to skip. To speak when silence feels safer.
Because if we are brave enough to see what others don’t, and to say what others won’t—we help the team reach places they’ve never reached before.
Not by keeping the project on track. But by making sure the track leads somewhere that matters.
And in a world where anyone can run a meeting or send a follow-up, we become irreplaceable—because we choose to see, to ask, and to stand where others don’t.
2024 taught us something profound: we are stronger with less. This year’s annual poster celebrates our choice to stay small, self-directed, and sustained—a “Company of One” built not by limitation, but by intention.
Piyorot Piyachan30 March 2025
For all of 2024, we navigated thick and thin with just two and a half people. Remarkably, we made more money than in 2023, when we were a 10-person team. What does this tell us? What message did the universe send?
We are stronger with less.
This was the most profound lesson of 2024: we thrive when we have less and do less. We are stronger when we remain true to our roots—true to who we are and why we do this. Choosing to stay small is not a limitation but a deliberate decision. Not because we can’t grow, but because we intentionally choose not to.
We find happiness in less. Less brings more of what matters. Less makes us unbelievably profitable. Less enables us to care deeply for ourselves and those we work with. Less ensures our longevity—so we can keep going, as long as we wish.
Being small is a rare privilege, one that few will ever experience. It’s not something to be ashamed of but something to celebrate. As part of this team, you are part of something special:
2025 is the year of the “Company of One.” I’m excited to continue building this strong and purpose-driven team with all of you. Let this poster serve as a reminder of what makes us extraordinary.
Enjoy the poster —and the year ahead.
To Keaw,
Thank you for being the creative soul behind our annual poster. Your taste, intuition, and quiet brilliance brought our story to life in ways words never could. Grateful for your presence—and your magic.
We Haven’t Come This Far without You.
Piyorot Piyachan17 March 2025
Mutrack is more than what we build—it’s the people who make it special. From big milestones, breakthrough ideas, and exceptional work to small gestures—a shared meal, a birthday surprise, a helping hand—every act of kindness matters. This space is for celebrating them.
For Sariya Saengcharoenwanakul, Business Development Executive, and Yosita Harsup, Product Development Specialist.
Thank you for believing in Mutrack when it was just an idea, for seeing the possibilities ahead, and for overcoming obstacles together.
I don’t know why, but I still remember vividly the first time I met you two at our (old) office almost seven years ago. And I don’t know why, but I knew almost instantly that you were the ones. Not because of your degrees, but because of the spark in your eyes as I talked about what Mutrack was.
Maybe it was because you were both so fresh, open, and eager to learn—that’s what fulfilled me the most. I had the chance to guide and support you as you grew professionally. But above all, I thank you for teaching me the greatest lesson in building a business: that it’s all about building a team.
Nan, I can’t even count how many times you’ve been so helpful to me and to the team. Thank you for joining Mutrack and for helping me build this company. The very first team member ever at Mutrack! But more than that, I have to thank you for everything we’ve been through—and for still believing in us.
You were always my go-to girl whenever I needed help. You were such an important part of this team—a spiritual leader with the biggest heart, the glue that held us together. It was my privilege to see you grow, to watch you navigate life, and to discover who you truly are. I wish you nothing but the best.
Thank you again for being so flexible and always willing to try so many different things with me. Keep up your great work—you will thrive wherever you go. I have no doubt that your future is bright.
Hi—the first-ever Product Specialist on our team. Yes, that’s you, Toey. Who would have thought? From an economics student to our product leader, working closely with the dev team—you made an incredible journey. You might not realize it, but everyone on the team admired and respected you. And not just internally, but externally too.
You were living proof that with the right space, freedom, and trust, experience and degrees don’t matter much. You brought fresh ideas to the table, faced your fears time and time again, and delivered great results.
Thank you for believing in me when I told you to switch to the product track. It was rough at first, but thank you for promising me, ‘I will try one more time.’ Yes—I still remember that Zoom session. Be proud that you never gave up on yourself.
Even today, I know in my heart that it was the right decision. You have the instinct and taste to become a great product person. If the universe allows, you’ll be the first person I call to take on this role at Mutrack again.
The first two team members—you became legends of Mutrack. The two I shared the deepest bond with. Thank you for giving me one of the most cherished experiences of my life.
For Yuparat Changjan, Data Scientist (Intern), Suphawadee Jaroenmitmongkhon, Data Scientist (Intern), and Nuttanicha Komkhum, Data Scientist (Intern).
Thank you for giving us big reasons to keep going and the hope that we can create something better for our nation.
I think the three of you know just how much we enjoyed our time together—the challenges, the obstacles, all the praises and laughs, and even a few tears… and most importantly, all the meals we indulged in. I’m pretty sure we all gained a little weight along the way!
At the beginning of this internship program, I had no expectations other than getting to know you three. I simply wanted to share what I know and believe, to tell good stories from my experiences, and to hope that, in some way, they would resonate with you. My only goal was to guide you in discovering what you truly love as data science students.
What I received back from you was nothing short of a miracle—far beyond anything I could have ever asked for from a group of interns. Time and time again, you showed me what it means to never give up, to step outside of your comfort zones, to work as a united team, and to be humble enough to embrace failures with grace. I couldn’t be more proud of the incredible women you have all become.
You were the creators of MMN—the May, Mar, Nut processor—which became the foundation of our intelligent assistant. Your work was novel, creative, and highly valuable, both in business and academia. You stepped into unknown territory with boldness and commitment, and that’s why so many people outside admired you.
But that couldn’t compare to the feeling of accomplishment. We introduced you to a way of working—one we wholeheartedly believe is the right way. Small, nimble, mission-driven. I had the privilege of watching each of you grow, discovering more about yourselves and what you truly enjoy. From the first day to the last, it became clear to me that you had all gained more confidence in yourselves. And that was the whole point of the program. It was never about me or even Mutrack—it was deliberately designed for you.
In return, you three gave us the greatest encouragement of all. You showed me that we can still put hope in the younger generation. The kindness, humility, respect, and courage I witnessed in you reminded me why this matters. It inspired me to do more—to continue the internship program, to seek opportunities to work with fresh minds like yours, and to keep believing in the future we can build together.
No one knows what the future holds for each of us, but I have no doubt that you will thrive in whatever path you choose. This program gave us a profound memory - whatever may come, this version of ourselves will live forever.
Good luck, MMN. Mutrack will always be home.
For Supatcha Vichitranon, Product Marketing Executive.
Thank you for making me cry—from the joy of seeing you shine. Your work reminded me that believing, mentoring, and waiting was worth it.
This is a deep secret I rarely share.
Throughout my life, when it comes to work, there have only been two moments that made me feel so emotional I could hardly speak. Two moments when a sense of pride ran through every fibre and every bone in my body. It may sound like an exaggeration, but it’s not. And strangely, neither of those moments were about winning the biggest contract, being featured in the press, or receiving any award. It was something much deeper.
The first moment happened during the first month after we founded Inthentic, my first company. I walked into a bank to transfer our very first salaries to two teammates who had believed in us from day one. That money left our account—but what filled me was pride. I felt something I had never felt before: the happiness of giving, of being able to provide. That transfer wasn’t about money. It was proof that I could take care of someone. That I could create something meaningful. That I could change someone’s world—through work, through respect. And yes, that moment made me cry.
Since then, I’ve been waiting to feel something like that again. To have a moment that reminded me I’m still on the right path. That I’m building this team with love and integrity—and that it means something.
I never felt it again… until the day I read that draft.
That statement. Your statement. The one you wrote for Vana.
You may have already forgotten it. But I never will.
I was sitting on my couch, reading, when that familiar feeling started rushing through me. And before I even realized it, I began to cry—not from disappointment, but from overwhelming happiness.
Your statement wasn’t just beautifully written. It brought me back to the very reason I started all of this. It reconnected me to my roots—why I choose to lead this way, why I invest so much into people.
It was the best kind of reminder—that all the effort was worth it. The teaching. The mentoring. The nurturing. The quiet support. And the waiting. The long, patient waiting for someone to shine in their own time, in their own way.
And you did. You shone in the most beautiful way.
I was moved—not just by what you wrote, but by you. As a person. As someone who had come into her own.
That moment will stay with me for the rest of my life.
Yaya, our little sister—you’ve always had a different character from the rest of the team. You came in as a shy girl, unsure of what you could contribute. But it didn’t take long for me to notice something you might not even realize about yourself: you’re a natural leader.
You’re the one who knows how to plan, how to organize, how to move things forward. You did so many things not because someone told you to, but because something inside you drove you to do it.
You are a self-starter. Be proud of that.
I wish nothing but the best for you. It’s been a joy to watch you step forward and grow—both professionally and personally.
You’re the only team member who’s ever made me cry. You did good here. You really did.
Thank you for one of the best memories of my life.
Building a business, we learned, is all about building a team. To everyone who has been part of Mutrack, those here today, those who have moved on, and those still to come: thank you. Mutrack will always be home.
PiyorotCEO of Mutrack
Work on meaningful problems with good people.
Piyorot Piyachan17 February 2025
We’re a small team 
focused on building great products that solve real problems in thoughtful and meaningful ways.
We care about the details, the impact, and the people we build for. If you enjoy thinking deeply, creating with purpose, and making things better, you might find a home here.
Mutrack is built on clear principles that reflect how hospitals actually operate, how people really work, and how lasting improvement is achieved.
Hospitals do not operate as isolated departments or standalone workflows. They function as interconnected systems—where people, spaces, equipment, and time continuously influence one another.
Operational problems rarely stay where they appear. Patient delays surface in wards but originate in transport. Equipment shortages show up in procedures but begin in circulation, visibility, or timing. Optimizing one area in isolation often pushes friction elsewhere instead of eliminating it.
Mutrack starts at the system level. By connecting movement, availability, and workload across departments and roles, it allows improvements in one part of the hospital to strengthen the whole—rather than shifting bottlenecks downstream.
This is why system-level clarity creates results where point solutions cannot.
Hospital operations work because of people—professional judgment, experience, and coordination under pressure. Technology that ignores this reality may look efficient on paper, but often fails in practice.
Many systems are designed to maximize control, compliance, or reporting. In real hospital environments, this approach creates resistance, workarounds, or silent disengagement. When staff feel monitored rather than supported, the system gradually loses accuracy and usefulness.
Mutrack is designed around the people who do the work. Visibility is provided to reduce uncertainty and friction—not to replace judgment or enforce rigid behavior. By respecting roles, context, and professional autonomy, the system supports coordination that feels natural instead of imposed.
This is why human-first design leads to adoption, trust, and sustained use—where control-first systems eventually break down.
Incremental improvement focuses on making existing processes slightly better. In hospitals, these gains often plateau because they operate within the same constraints—fragmented workflows, delayed information, and heavy reliance on manual coordination.
10X improvement takes a different path. It redesigns the structure that creates those processes, addressing friction at the system level rather than optimizing individual steps.
Mutrack enables this shift by removing hidden effort—searching, waiting, checking, and rework—through automation and real-time operational intelligence. Improvement comes from alignment across people, space, and time, not from pushing staff to work harder.
This is how progress becomes sustainable without placing additional strain on people.
We work hard every day to build a modern, supportive workplace for amazing people like you. That’s why we offer competitive salaries and a comprehensive benefits package for full-time employees, including time off, health insurance, and educational opportunities for career growth.













From the very beginning, we’ve been a remote-first team. We believe in flexibility while staying connected and productive with the right tools to help you do your best work—wherever you are.
Whatever team you’re on, your ideas and contributions matter. You’ll play a key role in creating exceptional products and experiences that make a real impact.
You won’t be the same person after working with us. We support continuous learning and happily reimburse members who buy books, attend professional conferences, or take courses to develop new skills.
Giving back is part of our culture. Whether it’s charity work, knowledge sharing, or team outings, we always make time for offsite trips, lunches, and monthly group dinners to strengthen our bond beyond work.
Every year we open one class of data science interns. It’s a co-op, four to six months with us, and the work is about the future: products and features we don’t have yet. Each class receives an assignment letter before it starts. Where the work leads is theirs to discover; sometimes it stays on course, sometimes we change direction together.
Precision in Motion
Can we build a copy of a hospital good enough to break on purpose, a thousand times, so the real one never has to?
Two places, one for the Simulator and one for the Optimizer, opening in November.
AI that matters
Can we teach an AI to write a performance report that actually helps someone?
They stayed on course. What began as a generative report became Mu, our operational intelligence.
The Worker Model
A system that doesn’t just count tasks but truly understands the people performing them.
In the first week, we decided together to change direction, to Roster. Their ideas shape it.
The R4 Project
To use the data to answer some questions nobody has asked before.
Prediction models for porter jobs at each hub and location, which inspired Class 25 to carry on into Roster.
Interested in joining us? Just tell us a little about yourself through our contact form. No formalities needed—we’d love to connect!
Eight guiding principles that define how we think, work, and grow—together—at Mutrack.
Piyorot Piyachan16 February 2025
Why “practice”? You may ask. It’s because this word implies attempts, changes, evolution, and the ongoing effort to be better than yesterday.
The list you’re about to read is by no means a fixed set of rules. These are things we have been testing, using, and implementing for a while—and we kind of like them.
But don’t expect them to stay this way forever. In five years, Mutrack will be quite different from today—because of you, because of all of us. So, be mindful in practicing them, observant about what works and what doesn’t, and brave enough to share if you see a better way to do things.
Tell me—I will appreciate it a lot.
This sentence was coined by Seth Godin—one of the greatest marketers of all time and, more importantly, one of our biggest influences. It has driven us immensely to do great work and take pride in who we are.
“People like us do things like this” carries two meanings.
The first is about our end results—the products and services we offer to the world. We always have our own perspective, process knowledge deeply, analyze problems thoughtfully, conceptualize better solutions, and create meaningful contributions. We share what we build with generosity. Our work is not just output—it represents us, a group of dedicated people striving to push the community forward.
The second meaning is about how we work. We value freedom more than money or fame. We thrive on independent thinking, performing at our best when we follow our mission—not someone else’s. We create for the niche (people like us), not for the masses. We refuse to conform to environments that don’t align with who we are.
With these two meanings in mind, be proud of what you do, what we do, and who you are. Don’t be afraid to stand by what we believe. Don’t feel guilty for saying no to things that compromise us. Don’t hesitate to walk away from the biggest company in the world if they try to control us.
We have practiced this since day one, and we still love it today. This is what Mutrack is about—driven, committed, and unapologetically true to who we are in a world full of noise and imposters.
And people like us do things like the following.
What kind of work interests us? How do we choose which projects to take on? While I can’t explain every detail in this section—you’ll learn them along the way—I do have something important to tell you.
At Mutrack, our decision-making process is guided by a simple but powerful question:
For this thing to happen, are we the only team capable of pulling it off?
We (at least I) ask this question because, at our core, we don’t want to waste time on projects that anyone can do. A simple website? Another generic mobile app? Just another chat software? No thanks. That’s boring work. If you ever find yourself deciding whether a project is worth our time, ask yourself: Are we the only team—the best team in the world (or at least in this country)—that can execute it with true excellence?
If the answer is yes, congratulations—this project might be worth our time.
This is a winning mentality we must practice every day. We won’t win every match, but if we choose to play, we play to win. We fight until we win. We must win so decisively that competing against us—or choosing not to buy from us—becomes foolish.
That means we never give up. We are prepared to fail and try again. And fail. And try again. We keep going.
That’s why you will hear a lot of NOs from me and the team. Not every opportunity is worth it. Only a few projects excite us enough to commit ourselves to making them real.
And when we do, you’ll hear customers and partners say—over and over—that our solutions are the best in the market, with no close competitor.
Whatever we choose to do must have the potential to be the best in the world.
I’m going to say that again—“the best in the world.”
That is the standard you need to uphold. That is the standard you need to improve.
If we want to build a world-class product—and we do—we cannot measure ourselves against what the local market offers. We cannot just take a spec and start coding. We cannot simply nod and execute exactly what customers ask for.
We have our own standard—a very high one.
We compare ourselves with world-class organizations, not local competitors. We aspire to be like Apple (aesthetic), Airbnb (UX design), Lego (simplicity and intuitiveness), and more. This list may evolve, but the core principle remains: we aim to be a world-class player in whatever we choose to do.
Your job is not to compare your work with direct competitors. “Hey, their UI looks like this—why not follow them?” Oh, you have no idea.
In enterprise solutions, user experience is rarely the focal point of selling. From day one, we’ve asked, why not? That’s why we (at least I) never study competitors’ products to see what features they have or how they design them—it’s a waste of time and an open door to distractions.
Instead, we must think for ourselves about what customers truly need to solve their problems. We must think about what the best companies in the world would do to conceptualize, design, and develop their products. That’s our starting point. That’s the level we must operate at—in every task, every project, every decision.
We compare ourselves with ourselves. We improve every time we get the chance.
Everything. Every time.
Only you know if you pushed harder for a better outcome. You cannot lie to yourself. So ask yourself—is this the best I can do?
Keep going. Keep raising the standard. Our team depends on it.
We always have strong opinions about what we do. We are an opinionated company. That means we operate with a clear set of beliefs and values—ones that shape our vision and direction.
We are not a “Yes” company that blindly follows customer demands. In fact, we are quite the opposite. We do not compromise our vision to close a deal, no matter how big it is.
These beliefs guide us. They help us stay true to ourselves, work on our own terms, use our own methods, and celebrate success in our own way.
No, this isn’t arrogance. On the contrary, we build this company with love—for our customers, our users, and our community. We commit to creating a better future for them, but we cannot do it for everyone. That’s why we must be opinionated—to know exactly who we serve.
Our job is to define “us” and find “us” in the world.
This process may be slow. It may take time to find customers, partners, and communities that believe what we believe. But it’s the only way to create meaningful change. The kind of change that moves society forward.
Be opinionated, but generous.
They are waiting for us to lead and show a better way.
People often get distracted by short-term trends. They ask what’s hot right now, what technologies will dominate this year, or which direction the market is heading. While these questions may sound exciting, they don’t help us build a strong, enduring company. Why?
Because, as Jeff Bezos once said, we can’t build our future on things that change rapidly. Do you agree? Instead, we must dedicate ourselves to mastering something that people will continue to value for years, even decades, to come. For us, that is our ability to deeply understand customers.
Here’s a secret I’m happy to share with you: every time we’ve successfully won over customers, partners, or stakeholders, it wasn’t because we were the biggest, the cheapest, the most technologically advanced, or the best-connected. It was because we understood them better than anyone else.
But when I say “understand,” I don’t mean blindly following their requests. Quite the opposite. We guide them toward better ways of doing things.
You will be surprised at how much this sets us apart. You will be amazed at how low the industry standard truly is. While other companies approach customers asking what to do and then follow instructions without question, we do the opposite. We enter with opinions, expertise, and a clear vision.
Because we invest heavily in understanding our customers, every conversation we have with them is fundamentally different. We speak from real experience. We share as true experts in our field. We show that we are genuine thinkers, builders, and problem-solvers.
And we know we’ve done this right when customers and partners are willing to wait for us—because they trust that we’re worth it.
This is our competitive edge. We must never lose it. We may not win every deal or every customer, and that’s okay. But it is our job to defend this ground at all costs.
No matter how big, rich, or well-connected a competitor may be, we must be the best at understanding and leading our customers. This is not just a strategy—it is our survival. Never slack on this.
As much as we admire the concept of a flat organization—one without managers or hierarchy—implementing it is incredibly difficult, and we might never fully get there. That said, everyone at Mutrack works collaboratively. No one operates in isolation. At the same time, everyone has a title—junior of this, senior of that—so hierarchy inevitably exists in some form.
You will learn how to navigate our structure and make an impact. You will be supported by senior members and leaders, and at some point, you’ll likely be guiding someone else, too. We all share the responsibility of looking out for one another.
But here’s what “best idea wins” means: no matter your title or position, your voice matters. Hierarchy may exist, but decision-making is not dictated by authority alone. We actively encourage everyone to think, speak up, and contribute. No decision will be forced upon you without explanation. Even I, as CEO, will never do that.
If something involves you, we want your thoughts, your ideas, and your suggestions. We value the best idea—even if it comes from the most junior person in the room.
You are here for a reason—because you’re not only great at what you do, but also a good person, and we depend on you to drive us forward in your area of expertise. It would be a terrible idea for us to dictate how you should do your job when we don’t know it as well as you do.
So, speak up. Share your thoughts. Engage in discussions. Criticize the idea, not the person. If your idea isn’t chosen, accept it with grace and commit yourself to making the best idea a reality. Learn from mistakes, iterate, and come back stronger the next time.
No one in this team is smarter than all of us combined. I am not the smartest person in the room, and I never try to be. You shouldn’t either. We work as a team, and your contribution is essential to our collective success.
Spend time with us, and you will learn how to be a true gentleman or gentlewoman. It all starts with being respectful and being respected.
Everyone here always shows respect—to every team member, customer, partner, and anyone who interacts with us in any way. It doesn’t matter whether they are big or small; showing respect is one of the most noble manners we can extend to others.
The list goes on, but you get the idea.
You will experience this yourself—being respectful makes you stand out. Most importantly, it makes you proud of yourself. People will notice that you are different, professional, and trustworthy. They will want to work with you more. You will attract all the best things by being respectful. We value this immensely.
Now, here comes the other side of the coin—being respected.
While being respectful, you must also ensure that you are respected. In most cases, these two go hand in hand: when you extend respect to others, they return it to you. When you act professionally and empathetically, people will respect you.
But remember this—don’t seek to be liked by many; seek to be respected.
What’s the difference? A lot.
Being liked means doing whatever it takes to make someone happy. You say “yes” all the time. You follow, chase, and make yourself available. You become an option—taken for granted.
Being respected means standing by your own ideas, mission, and plans. You seek common ground where both sides benefit. You don’t follow, chase, or try to be chosen—you make your own choices. You decide whether to work with someone or not. You continue to deliver great work and uphold professionalism, even when it means saying no.
When you operate at this level, people will start to respect you.
We need you to remember this.
Don’t chase being liked. Give people reasons to respect you. That’s what will take you far.
We designed this company to be calm. We don’t believe in a work environment driven by urgency and chaos. We rarely have emergency meetings, critical red issues, explosive deadlines, or life-or-death decisions. We have never had a fight or even raised voices at work. Why? Because the processes, culture, and people here make it so—by design.
When we are united and prepared to face any situation together as a team, there’s no need to make things bigger than they should be.
To be a calm company, we choose to:
Your job is to absorb this value into your work life. Remind yourself that most tasks here are not life-threatening. Of course, once in a while, we may face an urgent issue, but you must compose yourself, stay calm, and trust that the team is there to support you all the way through.
Calmness is contagious.
When we show it to the outside world, we teach others that working with us is a pleasant experience. Because we hold ourselves to a higher standard of conceptualization, planning, management, communication, and problem-solving, others can rest assured that things will be fine in our hands.
These eight practices shape who we are today. I believe they will continue to guide us well into the future. It’s up to you to take care of them—to uphold them, refine them, and make them stronger.
The more we practice, the better we will become as a team.
Thank you for being here and believing in us. Let’s make our time together truly worthwhile.
Get to know us better—our why, mission, and the journey we’re heading.
Piyorot Piyachan15 February 2025
At its core, Mutrack is a technology company specializing in enterprise software development and tracking technologies. We are passionate about building a smarter, more efficient digital platform—one that empowers better decision-making and helps businesses move forward.
As a small but dedicated team, we bring different perspectives to every challenge we take on. Our strength isn’t just in what we know—it’s in how we think, create, and commit to solving meaningful problems.
Every year, the U.S. healthcare system loses up to $935 billion—with $265.6 billion wasted on administrative inefficiencies and operational hurdles alone. These challenges aren’t unique to the U.S.; hospitals in Thailand face similar struggles. From complex workflows to fragmented data systems, inefficiencies continue to drive up costs, strain hospital staff, and impact the quality of patient care.
30-40%Medical equipment utilization rates can be as low as 30%, especially for movable assets.
72 minutesNurses spend 72 minutes per shift just searching for equipment needed to perform services.
121 minutesPatients wait 121 minutes for the full process—half of this time is lost due to paperwork and handovers.
50%Every year, 50% of vaccines are wasted globally due to poor logistics and temperature control.
$3 millionA single U.S. hospital department could waste $3 million worth of medical supplies annually.
$10,000Hospitals unknowingly lose up to $10,000 per month in linen costs due to poor asset tracking.
Better decisions require better data. Hospitals deal with high complexity and waste, but it doesn’t have to be this way. With the right technology, healthcare teams can see more, know more, and act faster—cutting waste, improving productivity, and making confident, data-driven decisions.
That’s why we built a smarter way to work—where hospitals can track people and assets, monitor real-time usage, and gain insights that drive action. One system, one source of truth.
Real-time insights, location-based data, and predictive analytics help teams make the best decisions—faster.
Mobile connectivity, Cloud computing, IoT, AI, and automation come together to transform operations effortlessly.
Seamless, human-centric workflows and real-time access empower hospital teams like never before.
Imagine a future where better decisions lead to better lives—where every bit of active and passive data helps us learn, evolve, and unlock our full potential.
At Mutrack, we are building that future. By blending IoT and Big Data, we empower people with accurate, real-time insights and trustworthy recommendations to navigate both day-to-day operations and long-term strategies more efficiently.
When they see more and know more, they can become more—and that’s the future we’re shaping.
We live in a world where great things are built on purposeful missions and trust. At Mutrack, we are committed to building a sustainable company that benefits both our team and the world around us.
We often come across good opportunities that come with certainty and obvious answers. But that’s not what we seek. We aim for great opportunities—ones that challenge us to innovate and create something significantly better.
We make simplicity a priority. Not just in designing easy-to-use products, but in how we work and collaborate. Everything we do—interactions with co-workers, users, customers, partners, suppliers, and our community—should feel effortless and intuitive.
We think and act independently, guided by original thinking. We don’t follow trends or look to others for direction. We choose to see the world through our own eyes, make decisions based on what we believe is right, and build things in our own way.
These three guiding principles shape our mindset, but how do they translate into everyday work? We’ve defined 8 Things We Practice—a set of working principles that reflect how we collaborate, make decisions, and move forward as a team.
Reasons and principles mean little until they become something people use every day. So far, ours have become five Applications, built on our own hardware and software. With each one, the people behind the care see a little more and know a little more. And we will keep working to make them better.
If you, too, believe in upgrading our healthcare system for more productivity and less waste, let’s make it happen together. Be a part of Mutrack.
This is a letter to celebrate the time we shared, the things we built, and the quiet moments that meant the most. Three people, three stories, and a chapter I’ll always carry with me.
Piyorot Piyachan26 September 2024
From a shy girl, who smiles a lot, to a more confident one. You have made an impressive transformation, doing things you never imagined you could have done.
From the first week and the first month of unfamiliar environments to now - the day that you realize that every obstacle has its own way to be overcome. Because you proved that you could. We could, as a team.
From an unknown and unclear way forward to the point where your road starts revealing itself. You begin to see that life is full of opportunities and options, which only you can choose.
Momentum is the product of an object’s mass and velocity. The mass is what you love doing. It is the place where you feel most yourself. I believe you have tasted some of that with us. Then comes the velocity. It is how you have moved through the world thus far. How many times have you done what you love? How well did you do it the last time? How do you think you can improve next time?
One thing to always remember is that you have created a momentum of your own—a promising one. It is up to you now to keep it going and growing. Don’t be afraid to fail. That is the only way to succeed.
It is absolutely my privilege to see you grow. We are proud of you.
Piyorot Piyachan — A team member, problem solver, and most of the time a leader at Mutrack
I wholeheartedly believe that only creators can drive the world forward. From what I have seen, you are definitely a creator and you can be among the top. What is unique about you is your combination of a strong technical background and leadership skills. That is a huge asset, one I am certain will take you as far as you want to go.
Data is as much an art as it is a science. You have experienced this firsthand with us. Data is nothing without creativity, and this is where you will shine the most.
Keep leveraging your curiosity. Keep asking big questions. Keep pushing boundaries. It is the creator’s job, and the world needs that more than ever.
In five years, you will have a team of your own, working on innovative projects. I hope you lead with empathy, putting love first. Be a role model for your team. Inspire and challenge them to achieve extraordinary things. And show them not to fear failure, because you know better than anyone that it is the only way to succeed.
Last, but most importantly, as you travel the world building your career and your life, don’t forget Thailand—our beloved country. You are part of the new generation we can count on. You can become one of a few who helps uplift our nation and make it flourish.
I am proud of you. We are all proud of you and cannot wait to witness the future you will create.
Piyorot Piyachan — A team member, problem solver, and most of the time a leader at Mutrack
Hi sweet girl, I am sure you felt good being with us, and I believe you felt good about yourself too. Not because you fully accomplished everything you set out to do, but because we had the chance to do many things together. Some of which you can look back on and proudly say, “Yes, that was me creating that.”
It is better for you to say, “Yes, I tried my best to make that as good as possible for the team.” This sentence says so much about you—not that you weren’t afraid, but that you did it anyway, time and time again. It’s an admirable trait of yours. I am proud of you for never stopping trying.
Remember that no one can force you to do anything. To progress, you have to want to do it yourself. You know it won’t be easy crafting meaningful work, but you can create a space of your own—one where you don’t need to compete with anyone, where you can be yourself with your own unique set of skills. You have the power to set your own journey and destination.
If you wanted to do something — anything — successfully and you had no instructions, no role model, no road map, no mentors, all you needed to do was look around at how the majority was doing that thing, then do the opposite — because the majority is always wrong. — Earl Nightingale
You have a bright future ahead. Remember the conversation we had that day. Be courageous in thinking and acting differently, with kindness. Be brave enough to say, “People like us, do things like this.” I am excited to see you grow.
This is not a forever goodbye so don’t forget to check in sometime.
Piyorot Piyachan — A team member, problem solver, and most of the time a leader at Mutrack
Reflections from the Regional IoT in Healthcare Summit: despite low engagement and a sales-heavy focus, meaningful moments with students and my team reminded me why we do what we do. Grateful for the lessons—and more intentional about where we show up next.
Piyorot Piyachan20 August 2024
TL;DR: I attended a Regional IoT in Healthcare Summit in Bangkok to showcase Mutrack, our real-time location technology. While the event had its challenges—such as lower-than-expected engagement and a focus on product sales over meaningful dialogue—I found valuable moments, especially in interactions with students and my team. These experiences reinforced our mission to drive positive change through technology and mentorship. Moving forward, I’ll be more selective about the events we participate in, ensuring they align with our values and offer genuine opportunities for learning and connection. Despite the hurdles, I’m excited about the future and committed to pushing boundaries and inspiring change.
Why did I say yes to this invitation? Well, a few reasons:
But now, let’s be honest and take a step back to look at what actually happened.
Yes, it was free of charge to exhibit at the event. But that doesn’t mean it didn’t come with other costs—both financial and personal. I ended up investing in the booth, decorations, uniforms, lunch for the team (happy to pay), and other expenses. But more than anything, I invested my time and energy to make this the best event it could have been.
So, let’s be clear: there’s really no such thing as “free.” Every time we’re told something is “free,” it’s important to remember that it usually comes with its own set of costs, whether that’s money, effort, or the opportunity cost of what else you could have been doing.
This objective failed clearly. Thai audiences didn’t seem to understand the importance of “privacy” much. Was I surprised? Not really. Privacy in real-time location tracking is still a new concept in this country. I have a habit of doing things that most people don’t follow. I couldn’t help but lead the team to focus on the future, even if it’s something too far and difficult for others to see right now.
The most frequent questions about some of our features, like encrypted communication (during transmission and at rest) and dynamic identity protection, were whether those features are necessary. This sent a direct message to me that we have a long way to go in educating the market about the importance of privacy in real-time location tracking.
My answer? “It’s not necessary until it is.” Does that sound arrogant? Maybe. But it was the best response I could give without conflicting with my principles. The question implied that privacy is often overlooked when it comes to tracking. Most people don’t think about it until it’s too late.
In a normal situation, privacy and security don’t seem to be important. We doubt their value until we’re faced with a breach. People always find ways to cut costs and bring up arguments during price negotiations. But nothing is important until it’s too late. Privacy in tracking is the same thing. Imagine if your system is attacked and just a fraction of personal data is stolen. What would you feel? Would you ask yourself, “What if…?” If yes, then it’s too late to fix. Don’t let that happen.
No one wants to be tracked, which makes it the responsibility of decision-makers and purchasers to take privacy seriously when building or buying tracking solutions. It’s always better to overprotect than underprotect.
Privacy has been one of the three pillars of Mutrack since day one, alongside modularity and cost-effectiveness. It’s only recently that we’ve had the chance to truly work on it. At Mutrack, we firmly believe that when it comes to privacy, there is no middle ground. Either you commit fully to protecting it, or you don’t. Half measures simply won’t suffice. We must continue to make our community aware of this.
It’s not just us—privacy in real-time location tracking is becoming a big deal globally. With all the concerns about data breaches and how personal information can be misused, more people and businesses are waking up to the need for better protection. I think this growing awareness is going to work in our favor in the long run. As more people start to care about how their location data is handled, the way we prioritize privacy in Mutrack is going to stand out even more.
In general, visitors asked about Mutrack’s UI, and they seemed to appreciate the clean and modern design. They were intrigued by the Stealth Mode feature that masks the current location of people and objects. Some wondered how we can locate IT devices like laptops and tablets. We do so through Mutrack Agent for Windows and Android. A demo I gave made this clearer, but it seemed that none of them saw this as something they wanted. Understandable—I need to do better in explaining why Mutrack Agents are innovative and very useful.
I considered the objective to unofficially launch the concept of Private Real-Time Tracking to the public for the first time a failure. Am I being too harsh? Perhaps. My expectation was that we would get about ten visitors ready to sign up for a beta test. We got less than that. Just three visitors showed serious interest: two system integrators, who plan to propose it to their clients, and a Head of IT from a major university in northern Thailand. He has been building his own solution for over a year but admitted it’s not elegant or very reliable. When I showed him our price list, he was shocked and said, “It’s a great price.” At least I received valuable feedback on my pricing. I took that as a win.
There was another win when the same Head of IT asked if Mutrack works with BLE tags from other brands. “Yes, as long as it’s Eddystone,” I replied. He smiled big time. That moment confirmed that we’ve done a good job building Mutrack as an open solution, capable of connecting with other elements in the whole tracking ecosystem. It’s small wins like these that remind me why we’re on the right track.
I was told that around 150 top executives from Thailand’s top hospitals would attend, so I set my expectations very high. In hindsight, I realize that was a mistake—I was disappointed, big time. I’m not blaming anyone, especially not my team. If anything, I was overly optimistic.
Let’s do a quick calculation: Thailand has around 1,400 hospitals. If we consider that hospitals with more than 500 beds are large and have access to funds, that leaves us with just about 60 hospitals nationwide. Assuming each has around eight top executives—CEOs, COOs, and Directors—we’re talking about less than 500 people in total. What are the odds that 30% of them would be in the same room at the same time? Was I being delusional? In retrospect, yes.
Being on stage, I couldn’t tell how many of the audience members were top management. My best guess was no more than 20. After the session, three of them visited our booth. That’s a 15% conversion rate, which isn’t bad by today’s marketing standards. One out of those three immediately wanted to discuss collaboration with us—a 33% conversion rate from “qualified leads” to “in negotiation.” Not bad at all. My mistake was wishing for a lot more leads to start with. I had fancied having 100 top executives listen to my speech, leading to 15% visiting our booth (15 people) and 33% wanting to start a collaboration (5 people). In reality, I was off by a factor of five.
Reflecting on this, I realize that my expectations were set too high. In the future, I’ll focus more on engaging deeply with a smaller audience, rather than trying to appeal to a larger group. Quality leads are often more valuable than quantity, and this event reinforced that lesson. The few conversations I did have were meaningful, and the interest in collaboration shows that we’re solving real and pressing issues for them, even if the numbers weren’t as high as I’d hoped.
I had high hopes for the session, expecting it to be a platform where industry leaders could exchange knowledge, inspire innovation, and delve into the complexities of IoT in healthcare. Unfortunately, I felt that the session wasn’t effectively arranged to meet those goals. Instead of fostering an environment of learning and discussion, much of the time was devoted to selling products and solutions. The focus seemed to be more on promoting the latest offerings rather than engaging the audience in meaningful dialogue or presenting actionable insights.
As I sat through the various presentations, it became clear that, from my perspective, the session lacked depth. The content was heavily skewed toward product showcases and marketing pitches, which overshadowed any potential for educational value. While it’s understandable that companies want to highlight their innovations, I felt that the balance might have been off. There seemed to be little room for exploring the broader implications of IoT in healthcare or discussing the challenges and opportunities that lie ahead.
This approach left me questioning whether the audience—some of whom were top management from hospitals—would walk away with anything truly valuable. Of course, this is just my view, and others may have found the content more relevant to their needs. I couldn’t help but feel that the session might have missed an opportunity to inspire and inform these decision-makers about how they could leverage IoT in healthcare to improve patient care, optimize operations, and drive future growth.
Looking back, I realize that the session’s structure might have been driven by the event’s commercial interests, but it came at the cost of providing real value to the audience—or at least, that’s how it seemed to me. It’s a lesson in how important it is to strike the right balance between showcasing products and fostering an environment of learning and innovation. If I had the opportunity to influence the session’s format, I might have pushed for more interactive, discussion-based elements that encourage the sharing of insights and experiences, rather than simply promoting products and services.
I used to do this a lot in the past for physical and online events. But after stepping down from the stage this time, I realized that I don’t feel the same about it anymore. It’s not that I didn’t enjoy talking about my work and sharing insights from the inside—I still love that. But I’ve grown weary of being controlled by the constraints of a fixed topic and a strict timeline set by the organizer.
Not that I was too lazy to prepare. On the contrary, I worked very hard to give the best I could with all the knowledge I have. I wanted my content to be educational, inspirational, and insightful. I tailored my standard presentation on the Internet of Things for Hospitals and 10X Improvement with Hyper Location Aware Applications to align with the event host’s business and product direction. It was my way of paying respect and showing gratitude for the honor they gave me.
I wrote a word-for-word script, memorized it, and rehearsed my speech countless times. Yet, despite all this effort, I felt that I used to be better. I used to give better speeches. This time, I felt like I fell short. I’m not sure how others perceived it, but I was not happy with my performance at all.
During my 10-minute speech, I felt the pressure of the clock ticking away. There was so much more I wanted to say, but I had to stick to the script and ensure I didn’t run over time. It reminded me of why I’ve started to step back from these kinds of engagements. Speaking within such rigid parameters felt like I was sacrificing depth for brevity, and that’s not how I want to share my experiences or ideas.
“Please be on time,” the stage staff said.
“Don’t worry. I will finish my session at the perfect time,” I replied with full confidence, as I had practiced this many times.
“It would be great if you could finish early because the session has been running late,” the staff requested, asking me to cut it short.
I didn’t say a word as I walked on stage, reminding myself to stick with my rhythm. It was a real surprise when I saw a “Time’s Up” sign before I even reached the last slide. How is that possible? I asked myself while presenting. I was forced to cut it short, and I complied. I didn’t mention anything from the last slide, which contained crucial tips for utilizing the Internet of Things in Hospitals. My most important messages weren’t heard by anyone. Those tips weren’t just an afterthought—they were actionable insights that could have provided real value to the audience, helping them implement IoT in healthcare effectively in their hospitals.
I fully understood the stage staff—they needed to regain control of the schedule. Unfortunately, I became collateral damage. This was the main reason I felt unhappy with the outcome.
In the past, I might have embraced these challenges, seeing them as a way to sharpen my messaging. But now, I find myself craving more freedom in how I communicate—whether that’s through writing, direct interactions, or smaller, more intimate discussions where the focus is on real exchange rather than sticking to a schedule.
As I stepped down from the stage, I felt a sense of closure. I’m not saying I’ll never speak at events again, but if I do, it will have to be on my own terms—where I can engage without feeling rushed, and where the content is truly reflective of what I want to share, not just what fits into a pre-defined box.
For the exhibition, we wanted to create a booth that would not only showcase our products but also engage visitors in a meaningful way. We brought along a selection of our core technologies designed to help hospitals be more productive. These included our Linen Management System with RFID, the Indoor Job Dispatching System using BLE, and the highlight of the show—our Private Real-Time Location technology. Each of these technologies was chosen with a specific purpose in mind, to demonstrate our capabilities in real-time location tracking.
The centerpiece of our booth was a live demonstration setup. We had all our products in place, allowing visitors to see firsthand how our tracking solutions work. We put extra effort into creating an interactive experience with Mutrack. We planned a mini product tour, where we set up a few access points and our own locators to create an indoor tracking infrastructure. During the tour, we walked around the exhibition zone with BLE employee cards, BLE asset tags, a Windows laptop, and an Android phone.
This demonstration showcased our real-time locating capabilities, including some of our unique features like Zone-Based Alerts (“In Zone” and “Out Zone”) and Status-Based Alerts (“Active,” “Inactive,” “Out of Range,” and “Potentially Missing”). We also set up a small demo to show how our Dynamic Identity Protection works.
With the product mini tour, visitors could watch as employee cards and assets were detected, location changes were tracked, and updates were instantly reflected on the dashboard. This turned out to be a small success, as we were the only booth at the event that showcased products and technologies live.
Many visitors, both local and international, thought it was cool and took video clips while we were presenting. The live demos played an important role in ensuring that we could effectively communicate our value proposition within the limited time we had with each visitor.
Looking back, the booth was more than just a display—it was our chance to connect directly with people, show them the real-world applications of our technology, and hopefully leave them with a lasting impression of what Mutrack is all about.
Am I a salesperson? I think I am. But beyond that, I see myself as a change agent, someone who’s always trying to put our ideas out there for the world to see. It is our latest attempt to create a new wave in real-time location technology, one that prioritizes privacy, security, modularity, and cost-effectiveness. This event was my first real test of these ideas with a live audience, and I enjoyed it immensely.
The experience was completely different from being on stage. It highlighted the essence of personal connection, deep conversation, and engaging exchanges of ideas. Nothing beats talking face-to-face, where you can truly connect with people, understand their concerns, and share your vision in a way that feels authentic and impactful.
Many people stopped at our booth, curious about what we had to offer. The first question almost everyone asked was, “What is this?”
“We do tracking solutions for hospitals using Internet of Things,” I replied. And from there, the conversations began. My team and I had numerous opportunities to show how our solutions work, using real hardware and software. We conducted live demos in real-time—assets were detected, location change events were triggered, the tasks were dispatched to the mobile apps and the updates appeared instantly on the dashboard.
The visitors got a chance to interact with the technology firsthand, connecting it to their daily routines and envisioning how our solutions could address their pressing challenges. We discussed a wide range of topics candidly, exchanged ideas, and let our imaginations run wild without the constraints of time. It was the vibrant environment I had hoped for, one that made me feel truly alive. And my team felt the same way.
Interestingly, quite a few visitors asked if our platform could be extended to manage queues in a hospital’s check-up department. The main pain point was the ability to manage station queues in real-time and direct patients to the shortest queue possible to reduce waiting times.
I had researched this topic a few years ago, and my conclusion was that it was possible but not very practical. Even today, with advancements in real-time tracking technologies like Bluetooth Low Energy (BLE) and Ultra-Wideband (UWB), creating this kind of solution presents many critical challenges—not technologically, but practically and economically. As we know, BLE cannot be very precise; it’s difficult to determine if a patient is standing at counter A or counter B when they are just a few meters apart. UWB is very precise, but it’s also very expensive, and most mobile phones don’t support UWB.
Behaviorally, it’s also a big challenge to ask every patient to download an app and turn on Bluetooth. I told my visitors that if only 20% of patients comply with this requirement, a hospital would be investing in a solution that 80% of patients wouldn’t benefit from. They all agreed.
Another interesting case that came up during my discussions was whether Mutrack hardware, particularly our wristband, could help prevent patient falls. This is a significant concern in hospitals, especially with elderly or vulnerable patients. The idea of using Mutrack wristbands for fall prevention sparked a deep conversation about how our technology could be adapted or integrated with existing systems to monitor patient movement and detect falls in real-time. While we haven’t specifically designed our wristbands for this purpose, the conversation opened up new possibilities for how our technology could be used to address such critical needs.
My technical leader and I immediately started discussing the possibility of modifying our BLE firmware to detect posture changes, such as from still to moving or from sitting to standing. If these posture changes are detected, Mutrack could launch an alert to nearby nurses or staff, allowing them to quickly support the patient and potentially prevent a fall. This conversation opened up new possibilities for how our technology could be used to address such critical needs, and it’s something we’re seriously considering for future development.
I loved discussions like this. They were deep, engaging, and honest. I wasn’t trying to sell anything—just sharing my real experience and beliefs from years of working in this field. I’m confident that every single one of my visitors left with something valuable from me and my team. They walked away from the booth with new knowledge and insights, and many of them were inspired by what we do.
For the past few months, we’ve had the honor of welcoming three interns to our team. They are undergraduate students from the Faculty of Applied Statistics, with a background in data science, at a well-known technology university in Bangkok. Most of their days were spent on data science-related tasks, including data gathering, preparation, and creating forecasting models for one of our hyper-location aware applications. When I first heard about the event, I saw a great opportunity for them to experience a business environment for the first time. They were with us for the entire two days of the event.
The most valuable experience wasn’t mine; it was theirs, and I was proud to be a part of it. Free from their usual assignments, they were tasked with learning how we navigate this type of event. They occasionally engaged with visitors by greeting them at the booth, answering simple questions, demonstrating our products, and exchanging business contacts. Naturally, they struggled to manage all of this on their own and often turned to me and my technical lead for assistance. But the experience they gained from interacting with real people was invaluable. What they learned from this event will set the tone for their future development, particularly in communication and sales.
Right after the event, I asked them to give me a short report about their experiences, feelings, and findings. They all thanked me for the opportunity to experience new things that they couldn’t find in class. They agreed that they needed to practice speaking and storytelling more to build the confidence to handle challenging situations on their own. Their willingness to stay true to themselves, not give up, and seek ways to improve showed the right attitude.
I learned something from them as well while reading their reports. One of them wrote, ‘… some of the visitors didn’t seem to care how much effort we put into building great products.’ Curious about what they meant, I asked them to elaborate.
‘They sometimes overlooked the fact that we were trying to make all of our products easy to use, comprehensive, and automation-focused to effectively solve their problems,’ one of the interns explained. ‘They hoped that the products wouldn’t change how they currently work too much, wanted them to be inexpensive, yet still meet all their requirements.’
It was a finding that even non-experienced students could detect. I felt the same way and had known this for a long time. ‘What should we do?’ I asked them.
The interns recognized that it can be challenging to align customers’ perspectives with ours. They suggested that our main task is to clearly communicate our intentions and the purpose behind our products, showing how they address current issues. They believe that even if customers aren’t ready to adopt our solutions now, making a strong impression will lead them to consider us in the future when their needs change.
Regarding the budget, they felt that while some customers may think our products are expensive, they don’t necessarily see the full value of the advanced features we offer, like enhanced privacy and security. They noted that it’s difficult to shift the mindset of buyers or executives who might only be focused on immediate needs and costs. However, the interns emphasized the importance of maintaining our position and ensuring our products and company are recognized for their innovation. They believe that as the world evolves, customers will eventually see the value and come to us because we are already positioned for the future.
That’s the spirit of this team—never dropping our standards, always striving to solve problems with the right technologies, and standing firm in what we believe in. I was proud of how they all reacted to this.
They put in all the effort to make this event as successful as it could be. I made sure to thank them as well for staying with me throughout the entire show.
As they returned to their normal routine of working with data, I hoped they brought some inspiration from the event to their assignments. I hoped they could understand why we always push the boundaries of what audiences have experienced. I wanted them to feel the importance of their work in forecasting future patient transportation jobs, managing workloads, and planning worker rosters. Most of all, I hoped they felt proud to deliver a unique and valuable feature to our beloved healthcare users—something that truly stands apart.
This time, it was mine. The best feeling from the event didn’t come from closing a deal or receiving compliments from prospects and partners. It came from a conversation I had with third-year undergraduate students from the Faculty of Computer Engineering at a well-known university in the north-east of Thailand.
They attended the event as part of a field trip. The first group, consisting of 5-6 students, stopped at our booth, curiously eyeing the screen and hardware on the table. They seemed hesitant to step closer, so I took the initiative to start the conversation.
“We do tracking solutions for hospitals using the Internet of Things,” I briefly introduced them to our work.
“Can you explain more, please?” one of the students asked, prompting me to continue.
I spent about five minutes walking them through all of our products—the technologies behind them, the concepts that inspired their creation, the pain points we aimed to solve, and the hardware and software techniques we developed to overcome technical challenges. I spoke to each of them directly, looking them in the eyes, and I saw their interest sparking. The group grew larger as more students joined in, drawn by the conversation. They listened intently, took notes, and some even asked insightful questions, fully engaged with both me and my technical lead.
I vividly remember telling them, “We are not a software house, simply following what users want. We are a small technology company, dedicated to solving real challenges one by one for our customers through the use of advanced technologies. We take the time to study their processes, talk to as many customers as possible, and then engineer the best solutions to improve the way they work.”
Some of them nodded in agreement with our mission. Then another student asked, “Do you have intern positions open?” In that moment, I knew my technical leader and I had done a good job inspiring them. I handed over my business card, telling him to send me an email when he is eligible to apply for an internship. I also kindly reminded him to share my contact information with his peers.
After the first group left the booth, just a few minutes later, a second group arrived. I noticed some familiar faces from the first group—they had returned for our presentation a second time. Some students even brought close friends to talk to me again afterward. It was the best feeling I experienced during the entire event.
This is what my team and I are all about. We exist to bring positive change to our community through technology. We don’t just create products to make a living; we understand that our greatest responsibility is to help build up the next generation—those who will uplift our country in the years to come. My conversations with these students give me the strength to keep going and never stop. Every time I have the opportunity to share my personal experiences and beliefs—especially the conviction that only creators can drive the world forward, and that we must be those creators—I feel blessed and humbled to be here, fulfilling this life mission.
This was the proudest moment from the event, one that I will carry with me for a long time.
As I reflect on our experience at the IoT in Healthcare Summit, I realize that our success wasn’t just about showcasing cutting-edge technology—it was about embodying our core values. One of the eight principles we practice daily is that ‘Understanding customers is our biggest strength.’ This principle guided every conversation, every demo, and every interaction we had at the summit.
In today’s fast-paced world, people often chase after what’s hot, the latest trends, or the newest technologies. But as Jeff Bezos wisely pointed out, we shouldn’t bet our lives on things that change rapidly. Instead, we focus on something enduring—our ability to truly understand our customers.
Time and again, we’ve seen that our success doesn’t come from being the biggest, the cheapest, or even the most advanced. It comes from our deep understanding of our customers’ needs, challenges, and aspirations. This understanding allows us to do more than just follow their instructions. We show them a better way, inspire their future vision, and teach them how to solve problems more effectively.
At the IoT in Healthcare Summit, my team exemplified this principle in action. We didn’t just present our products—we shared our vision, our expertise, and our genuine commitment to helping our customers succeed. We engaged with visitors not just as vendors, but as trusted partners who think, build, and do with purpose. This is why customers and partners are willing to wait for us—because they know we see them, we care about them, and we lead them towards a better future.
I want to take a moment to thank my team for embodying this strength. Your ability to understand and connect with our customers is what sets us apart. We cannot afford to lose this edge, no matter how big, rich, or well-connected our competitors may be. This is our ground, and we must protect it at all costs.
So, to my team—thank you for your unwavering commitment to this principle. Thank you for making our presence at the IoT in Healthcare Summit not just a demonstration of technology, but a testament to the enduring strength that truly differentiates us. Let’s continue to be the team that understands, leads, and inspires, for it is this that will sustain us and propel us forward.
As I write this article, I find myself wondering: if a similar opportunity presents itself again, will I say yes? The answer isn’t straightforward. This event offered many valuable moments, but it also had its challenges.
If I were to say yes to a future event, it would have to meet certain conditions. First, the event must align closely with our mission—bringing real, positive change through technology, and providing a platform where we can genuinely connect with the audience. Second, the format should allow for meaningful interactions, not just brief encounters or rushed presentations. I need the opportunity to engage deeply with attendees, whether it’s through hands-on demos, in-depth discussions, or interactive sessions.
Finally, the event must offer something valuable to my team, especially the younger members. Whether it’s a learning experience, networking opportunities, or the chance to see the impact of their work firsthand, their growth and development are as important as any business objective.
If these conditions are met, I would consider saying yes again. Otherwise, I might choose to pass, focusing instead on opportunities that align more closely with our values and goals.
Moving forward, whether it’s through events like this or other initiatives, I’m excited about the opportunities ahead. We will continue to push boundaries, inspire change, and create a brighter future through technology.
If you found our approach to privacy-focused real-time location technology and hyper location-aware applications for hospitals interesting, or if something from our experience at the IoT in healthcare Summit resonated with you, we’d love to hear your thoughts. Whether you have questions, ideas, or just want to explore how our solutions could fit into your work, we’re here to chat.
Feel free to reach out to us to learn more about Mutrack, discuss potential collaborations, or simply share your perspective. We’re always eager to connect with like-minded individuals and organizations who share our passion for location technology and positive change.