# User Observe: Team Coordination in Indonesian Workplaces **Version 1.0 — June 2026** --- ## About This Document This brief profiles the real people experiencing team coordination friction in Indonesian workplaces. Rather than describing an abstract "user," it builds five distinct profiles grounded in actual workplace contexts — SME owners, middle managers, startup coordinators, field supervisors, and corporate knowledge workers. Each profile covers daily context, team structure, current workflow, core frustrations, active workarounds, and what a catastrophically bad coordination day looks like in practice. These profiles are based on research into Indonesian workplace culture, UMKM management challenges, startup ecosystem realities, and behavioral patterns documented in Indonesian professional communities. --- ## Profile 1 — The SME Owner-Operator **Who they are** Budi is 38. He owns a printing and design business in Bekasi with 11 employees — two designers, three production staff, two delivery drivers, an admin, a sales person, and a part-time bookkeeper. He started it eight years ago and runs it as a full-time obsession. He is on his phone from 6am to 10pm. His employees call him Pak Budi. **Team size and structure** 11 people across two physical locations (the shop and a small warehouse 3km away). No HR function. No dedicated operations manager. Pak Budi is the org chart. **Daily context** The day begins before he arrives. By the time he's in the ojek on the way to the shop, the WhatsApp notifications from last night are already stacking: a client wanting to change artwork on an order that goes to print today, a driver saying his motorbike broke down, and a designer asking if he can come in late because of a family matter. Pak Budi handles all of this — on the back of the ojek, one-handed. The shop runs on three active WhatsApp groups: "Tim Produksi," "Pengiriman," and "Pak Budi & Klien." There is also a separate WhatsApp group for each major client. And a personal chat chain between Pak Budi and each employee for things that shouldn't go in the group. At any given moment he is tracking 15–20 active conversations. Order tracking happens in a combination of WhatsApp notes, a physical whiteboard at the shop, and an Excel file that the admin updates — sometimes. When the admin is sick, no one updates it. When Pak Budi is at the warehouse, he can't see the whiteboard. The Excel file lives on the admin's personal laptop. **Current coordination workflow** - Orders come in via WhatsApp, Instagram DM, and occasionally email - Pak Budi verbally (or via WhatsApp voice note) tells the designers what to do - Designers send files via WhatsApp to Pak Budi for approval - Pak Budi approves verbally or forwards to client via separate chat - Production instructions come from Pak Budi to production staff, again via WhatsApp - Delivery scheduling is a conversation between Pak Budi and the drivers every morning - Payment tracking is done by the admin in the Excel file, or by memory when she's out **Core frustrations** Every decision goes through Pak Budi. Not because he wants it that way, but because there is no system that lets anyone else make decisions safely. If the designer sends the wrong version to print, it costs Pak Budi money. So he checks everything. The checking takes most of his day. The information that lives in conversations evaporates. A client change request that came through a voice note at 9pm is easily missed. When a deadline is missed, Pak Budi often discovers it only when the client calls angry — there's no system that shows him what's due today versus what's already done. He can't step away. He went to a family wedding in Yogyakarta last year and spent most of it on his phone managing a large order that went wrong while he was in the car. When he's not available — even for two hours — things stop or go sideways. Employees wait for him to tell them what to do next rather than taking initiative. This isn't laziness; it's the system. When someone once made a decision without asking him, it turned out to be the wrong decision, and Pak Budi felt the damage. So over time, everyone learned to wait. Now he is the bottleneck his own business created. **Workarounds in use** He puts order details in WhatsApp "pinned messages" at the top of each client chat, and re-reads them before calling the client. He screenshots important WhatsApp messages and saves them to a phone folder labeled "PENTING" (important). He uses voice notes extensively because typing everything is too slow. He calls instead of messaging when something is urgent because messages get buried. He has tried Trello once, after a cousin recommended it, but no one used it after the first week. **What a really bad day looks like** It's Monday. A large corporate client — 500 tote bags for a company event on Thursday — needed artwork approval by Friday. The artwork went to the client via WhatsApp on Thursday night. The client said "okay" in a voice note on Friday afternoon. Production started Saturday. Monday morning the client calls. Turns out "okay" on Friday was not approval of the final file — it was acknowledgment that the file had arrived. They want changes. The production run is 40% complete. The correction requires a new file, new ink mixing, a restart. The delivery deadline is now impossible. Pak Budi is also handling two other jobs due Wednesday, a supplier dispute over late payment, and his admin has called in sick. By noon he has sent 87 WhatsApp messages and made 12 calls. He has eaten nothing. The shop runs fine while he is there because his physical presence is the coordination mechanism. When he leaves at 7pm, two staff stay late to catch up. He pays them in cash from his wallet. --- ## Profile 2 — The Middle Manager in a Mid-Sized Corporate **Who they are** Sari is 33, a Marketing Manager at a consumer goods distributor in South Jakarta with around 400 employees total. She manages a team of seven: two brand executives, two digital marketing staff, one graphic designer, one events coordinator, and one content writer. She has a manager above her (the Marketing Director), a Director above that, and a VP of Sales who often has opinions about her team's work. **Team size and structure** Team of 7 direct reports. Sits in the middle of a classic hierarchical org chart. Has authority to plan but limited authority to decide — most external spend, campaign direction, or cross-department asks require her manager's sign-off, which sometimes requires the Director's sign-off above that. **Daily context** Sari gets into the office by 8:30am most days. The company uses Microsoft Teams — in theory. In practice, the Marketing Director communicates exclusively via WhatsApp. So Sari maintains two active communication layers: the official one (Teams, email) and the real one (WhatsApp). Her team has learned to check WhatsApp first. She is in meetings — rapat — for roughly three to four hours a day. Weekly Monday briefing with the Director. Weekly sync with the Sales team (almost always overrun). A regular agency call on Wednesdays. Ad hoc calls that get scheduled at 24 hours' notice via WhatsApp. She spends a meaningful part of her day preparing for, being in, or following up from meetings. The company has a formal approval process for marketing spend: requests go through a Google Form, get reviewed by finance, and require sign-off at various levels depending on amount. A campaign brief under Rp 5 million gets approved in 2–3 days. Above Rp 50 million it can take two to three weeks. But the market moves faster than the approval chain, which means Sari regularly has to present work in meetings using placeholder budgets, and finalize details after the fact. **Current coordination workflow** - Campaign briefs are created in Google Docs and shared on Drive - Tasks are assigned verbally in team meetings or via WhatsApp - Status updates happen in the WhatsApp group "Tim Marketing" - Design revisions go back and forth via WhatsApp (screenshots, voice notes, file shares) - Approvals from the Director come via WhatsApp message, rarely in writing - Cross-department coordination (with Sales, Logistics, Finance) requires sending emails to which no one replies, followed by WhatsApp messages to the relevant person's personal number **Core frustrations** Revision cycles consume enormous time and emotional energy. A single digital asset for a campaign might go through seven or eight rounds of revision — not because the brief was unclear, but because each round of approval surfaces a new senior stakeholder who has a different opinion. The designer revises. It goes back up. The VP of Sales sees it in a meeting and wants it changed. It goes back to the designer. No one documents what changed or why. The original brief is lost in a Google Doc that three people have edited in different directions. Approvals don't come back when expected. Sari sends something for review via WhatsApp and has no visibility into whether it's been seen, considered, or queued behind eight other things. Following up feels politically awkward — she doesn't want to look like she's pushing her manager. The norm is to wait, send a gentle "sekedar mengingatkan" (just a reminder) message after a day or two, and absorb the delay. Cross-department work is where coordination fails most visibly. The Sales team has different priorities and moves on a different rhythm. When Marketing needs input from Sales for a campaign, the ask goes into a group chat that Sales people check when convenient. When it comes back late, the timeline slips. No one is accountable, because the accountability mechanism is a WhatsApp message that everyone technically "saw." She is responsible for delivery but doesn't control the approval chain above her or the responsiveness of peer departments. This gap — between accountability and control — is the core tension of her working life. **Workarounds in use** She maintains a personal to-do list in her phone's Notes app because the official system doesn't capture her personal obligations within others' workflows. She screenshots approvals received via WhatsApp and saves them in a folder labeled by campaign name, because she has been in situations where a senior person denied approving something. She over-prepares for meetings — bringing printed materials that reflect the latest version — because she cannot trust that everyone has read the shared document. She builds two extra days into every timeline she presents to her team, knowing that approvals will slip. For cross-department asks, she has learned to make requests in person or in a meeting rather than in writing — verbal agreement in front of witnesses is more binding than a WhatsApp message. **What a really bad day looks like** There is a campaign launch scheduled for Thursday. The campaign creative was approved in a WhatsApp voice note by the Director on Tuesday. Sari's designer briefed the digital agency. The agency sends final assets Wednesday morning. Then the VP of Sales sees the final poster in the Wednesday all-hands meeting. He doesn't like the tagline — says it's "too aggressive." He's not in Sari's reporting line but he's senior and he has influence. The Director, who is in the room, says "let's revise." That's the decision. No written record. The launch is now at risk. Sari spends Wednesday afternoon in a scramble: reopening the brief with the agency, chasing the Director for a written steer (hard to get), and trying to figure out whether the social media posts already scheduled can be paused. The scheduling is done through a third-party tool that only the content writer has the login for — and the content writer is taking a day off for a family ceremony (hajatan). She reaches the content writer via personal WhatsApp. He is apologetic, responds from the ceremony, and pauses the posts while sitting at a relative's wedding reception. By 8pm the revision is done. It's approved via a WhatsApp voice note from the Director saying "udah bagus" (looks good now). No one is sure if that counts as final approval. The campaign launches Thursday. No one writes down what happened. Next month a similar thing happens. --- ## Profile 3 — The Startup Project Coordinator **Who they are** Dinda is 26, a Project Coordinator at a B2B SaaS startup in Jakarta with around 60 employees. The startup uses Slack, Notion, and Google Workspace. She is the "glue person" — the one who tracks cross-functional projects that involve Engineering, Design, Product, Sales, and Customer Success. She has no direct reports. Her job is coordination, not authority. **Team size and structure** Her direct team is 4 people (herself + 3 other coordinators/PMs), but she works across all 60 people in the company on any given week. She has influence without formal authority over any of the engineers, designers, or salespeople whose work she needs to track. **Daily context** Dinda's day is Slack. She opens it at 8am and it closes when she sleeps. By the time she's commuted to the office (the startup is semi-remote, 3 days in, 2 WFH), there are already threads to respond to in #product-updates, #engineering-squad, and four active project channels. She has personal DMs from two engineers asking for scope clarifications on tickets she created, and a message from the Sales lead asking when Feature X will be ready to demo. She works with a Notion wiki that has project timelines, a product roadmap, and sprint documentation. In theory, this is the single source of truth. In practice, the engineers update Jira (because that's where the actual work happens), the product team updates Notion (because that's where they plan), and the sales team has their own Notion page with different information, updated on a different schedule. Dinda spends significant time each week reconciling these sources of truth. She runs the weekly cross-functional sync. She preps the agenda in Notion, shares it in Slack before the meeting, facilitates the call on Zoom, and writes the meeting notes afterward. The notes go into Notion. Within 48 hours they are out of date because engineers pushed changes that weren't in the meeting. **Core frustrations** Her formal authority is zero. To get something done, she has to rely on relationships, persuasion, and the goodwill of people who are technically her peers but whose time is managed by other people. When an engineer is blocked on something that requires a design decision, and the designer is in a sprint planning meeting, and the PM is on leave — Dinda is the person trying to unstick the situation with no actual power to do so. The Indonesian cultural norm of not saying no directly complicates her work in a specific way. When she asks engineers for an ETA on a feature, the answer is rarely "we can't do this in the current sprint." The answer is "we'll try," or "maybe next week," or silence. She has learned that optimistic estimates in Indonesian professional settings often mean "I don't know" or "I hope so." Building realistic timelines when inputs are culturally softened requires her to apply a private correction factor to everything she's told. She is accountable to Sales for delivery dates that Engineering sets. Sales promises customers. Engineering slips. Dinda is in the middle with no lever to pull. Her tool stack is sophisticated but doesn't solve the accountability gap: Jira tickets can be in "In Progress" for weeks, and there's no cultural norm for an engineer to update a blocker comment in Jira when they're stuck. Notification overload is a real daily cost. She is in 22 Slack channels. The average Slack channel gets 15–40 messages per day. She cannot read all of it. She has developed a triage system: starred channels, keyword notifications, and a mental model of which channels to skim and which to actually read. Still, things fall through. **Workarounds in use** She sends follow-up Slack messages with explicit calls to action — "can you reply by EOD today?" — because open-ended asks disappear. She DMs engineers directly rather than leaving comments in Jira, because direct messages get responses faster. She maintains a personal "radar" document in Notion where she tracks items that are "waiting on someone" — because the official project tracking doesn't give her this view. She uses the Slack reminder feature liberally, setting reminders to follow up on items she suspects won't move on their own. For things she really needs from people who are hard to reach, she asks in person or in a meeting. The face-to-face request in an Indonesian workplace still carries more weight than a Slack thread or a Jira comment. **What a really bad day looks like** An enterprise customer is expecting a demo of a new analytics feature on Friday. It was promised by Sales four weeks ago — before Dinda even knew about the commitment. She found out via a Slack message from the Sales lead on Monday, saying "btw [Feature Y] is going to the demo on Friday right?" She checks Jira. Feature Y is in "In Progress." She DMs the lead engineer. He says the backend is done but the frontend isn't ready. She DMs the frontend developer. No response. She goes to the frontend developer's desk at the office. He's at a meeting. She waits. The meeting ends. He tells her the feature has a bug that he hasn't been able to reproduce consistently, and he didn't put it in Jira because he thought he'd fix it by the end of the week anyway. She has to tell Sales that Feature Y may not be demo-ready on Friday. The Sales lead is upset because the customer is a high-value prospect. He asks if there's a workaround. She asks Engineering if they can show a staging environment. The engineering lead says staging is broken this week because of another deployment. The conversation moves to WhatsApp because the Sales lead doesn't use Slack much. By Thursday afternoon, the decision is made to demo a limited version of the feature with a canned video for the part that doesn't work. Dinda has to coordinate four people across two tools to stitch this together, while also preparing the demo script in a Google Doc that three people are editing simultaneously with track changes turned off. The demo goes okay. The customer asks a question the limited version can't answer. Sales promises a follow-up. No one writes down what was promised. It will surface again in three weeks. --- ## Profile 4 — The Field Supervisor **Who they are** Eko is 41, a Field Supervisor at a logistics company managing 18 drivers across a delivery zone in Surabaya. He reports to an Area Manager who is in the city office. He is never in an office himself — his "office" is his motorcycle and his phone. **Team size and structure** 18 drivers across three shifts. The drivers range from 22 to 54 years old. Digital literacy varies enormously: the younger drivers use smartphones comfortably; some of the older ones use WhatsApp but nothing more complex. None of them use a laptop. **Daily context** Eko starts at 5am. His first act is reading the overnight WhatsApp messages from drivers reporting issues: a flat tyre, a customer who wasn't home, a package that got wet in the rain. He responds to each before he has eaten breakfast. The company has an official logistics app that drivers are supposed to use to update delivery status. In theory, every delivery is marked "picked up," "in transit," "delivered," or "failed" in the app. In practice, about 40% of deliveries are properly logged. The rest are reported via WhatsApp when Eko asks, or not at all until the end-of-day reconciliation. The Area Manager wants daily status reports by 4pm. Eko compiles these himself, chasing each driver for their count, reconciling it against the app (which is often wrong), and typing the summary into a WhatsApp message to the Area Manager. **Core frustrations** He is accountable for delivery completion rates that depend on drivers who don't fully use the official system. When a delivery fails and a customer complains, the inquiry chain comes back to Eko. He often has to reconstruct what happened from WhatsApp messages and driver memory, because the app log is incomplete. The app is designed for desktop review and loads slowly on older Android phones — the kind that several of his older drivers use. Features that work well in the city office don't work reliably in the field. The company's official reporting tools assume connectivity and a level of digital literacy that doesn't match his team's reality. He has no real authority to discipline — formal HR is at the office, not with him. When a driver consistently underperforms or doesn't update the app, Eko's options are to talk to them (which he does, carefully, within the relational norms of Indonesian workplace culture, without direct confrontation) or escalate to the Area Manager (which feels like a failure and creates conflict). He absorbs a lot of the coordination friction himself rather than escalating. The 4pm report to the Area Manager is the moment all the day's coordination failures become visible. If his numbers are off — if deliveries are missing from the app log, if a driver had an accident that Eko handled but didn't formally escalate — it shows up in the report. The report is the moment of accountability, not the daily coordination itself. **Workarounds in use** He has a personal daily log in his phone's Notes app where he records every significant event: driver issues, failed deliveries, customer complaints, and his own interventions. This is not an official system — it's his personal protection. When questioned later, he has a record. He calls drivers who haven't reported in, rather than waiting for the app update. He tracks his best drivers' completion rates in his head and leans on them to carry the team metrics. He has built personal relationships with drivers based on respect, social reciprocity, and occasional lunches he pays for himself — because the relationship is the coordination mechanism. **What a really bad day looks like** It is the day before Eid. Volume is three times normal. The company has sent extra packages but not extra drivers. Eko has 18 drivers running at maximum capacity starting at 6am. By 10am, three drivers have called with issues: one has a motorbike breakdown, one has been in a minor accident (no injuries but shaken), and one says a customer is refusing delivery because the package label is wrong. The Area Manager messages at 11am asking for an update. Eko is on the phone with the breakdown driver trying to redirect his packages to another driver who is already near full. He types a quick "update 30 menit lagi ya Pak" (update in 30 minutes ok Pak) and keeps going. By 1pm, the app is showing 60% completion, but Eko knows actual completion is closer to 75% because the drivers aren't updating the app in real time — they're driving. He is manually tracking which drivers he's heard from and which he hasn't, in a combination of his Notes app and his memory. He has made 34 calls today. His phone battery is at 18%. At 3:45pm he starts compiling the 4pm report. He sends voice notes to drivers he hasn't heard from, asking for their delivery count. Three don't respond. He estimates based on their assigned route. He sends the report at 4:12pm. The Area Manager says the numbers look low and asks what happened with the broken-down driver's packages. Eko explains. The Area Manager says this should have been escalated earlier. Eko goes home at 8pm. There are still seven unreported deliveries. He will figure it out tomorrow. --- ## Profile 5 — The Government-Adjacent Knowledge Worker **Who they are** Ratna is 29 and works as a Program Officer at an Indonesian NGO that manages government-funded development projects. She coordinates between a Jakarta head office, three field offices in Sulawesi and Kalimantan, and a government counterpart agency. She has a team of two assistants. Total people in her coordination sphere: around 25, across four time zones (WITA and WIT). **Team size and structure** Two direct reports. But her real coordination challenge is lateral and upward: managing document flows, approvals, and reporting that involves people who have no reporting relationship to her at all — government officials, field staff, and donor representatives. **Daily context** Ratna's work is defined by deadlines that are fixed (government reporting cycles don't flex) and processes that are deeply document-dependent. A project activity cannot happen until it has a Surat Keputusan (official decree), which requires approval from two ministry departments, which requires a Surat Permohonan (formal request letter), which requires her director's signature, which requires her director to be in Jakarta rather than traveling. The paperwork chain can take three to eight weeks. She manages this using email for formal correspondence, WhatsApp for actual coordination, and occasional video calls for field staff check-ins. The government counterpart agency communicates exclusively by formal letter and in-person meeting — email is unofficial in their culture. Cross-time-zone coordination with Kalimantan and Sulawesi is where information loss is highest. Field staff submit reports via WhatsApp voice notes and photos, because they don't have reliable laptop access or good connectivity. Ratna or her assistants transcribe these into formal report templates. The transcription introduces errors. The errors get caught in review. The cycle adds days. **Core frustrations** She is the translation layer between informal field reality and formal documentation requirements. The field staff experience is captured in voice notes and photos. The donor requirement is a 40-page formatted report with numbered annexes. The gap between these two formats is her daily work — and no tool helps her bridge it. The voice note cannot become an annex entry without human transcription, formatting, and cross-referencing. Approval chains stall on individuals. When her director is traveling, formal letters can't be signed. When the government counterpart's signing officer is on leave, documents queue. She has no way to escalate around the authority structures — doing so would violate the relational norms that make cross-institutional coordination possible at all. Patience and personal relationship maintenance are the only tools available. The three-time-zone problem is chronic. Jakarta standard meetings are at 10am or 2pm. For Kalimantan field staff, 2pm Jakarta time is mid-afternoon in the field — often when they are traveling between sites and unavailable. She has learned to schedule field check-ins very early (7am Jakarta, 8am Kalimantan) or via asynchronous voice notes. She carries institutional memory that isn't written down anywhere. When a field officer was replaced last year, three months of context had to be rebuilt through conversations because the previous officer's knowledge lived in WhatsApp chats and her own head. **Workarounds in use** She maintains a shared Google Drive folder with all formal documents organized by date and type — but only she and her assistants use it; the field staff don't. She has a personal tracking spreadsheet for document approval status: column headers are document name, sent date, approval required from, status, last follow-up, and next action. She prints physical copies of important documents when visiting the government counterpart agency, because digital files are not treated as official. She schedules bi-weekly video calls with each field office as relationship maintenance, separate from formal reporting — because relationships are what make the informal coordination work when the formal system fails. **What a really bad day looks like** A quarterly field monitoring report is due to the donor on Friday. The report requires data from three field offices. Ratna sent the data templates to the field offices two weeks ago, with a collection deadline of Tuesday. It is now Thursday. Two field offices sent partial data on Tuesday, incomplete and in inconsistent formats. The third field office in Kalimantan sent a voice note on Tuesday saying they'll send the data "besok" (tomorrow). Wednesday came and went. No data. Ratna calls the Kalimantan field coordinator on Thursday morning. He apologizes — a village community event took priority this week, which is legitimate and not contestable within Indonesian cultural norms. He will send data today. It arrives at 2pm, via photos of handwritten sheets. Ratna and her assistants spend the afternoon manually entering and checking figures. At 4pm she realizes one of the indicators from the first field office is blank — they forgot a column. She messages them via WhatsApp. No response. She calls. The field officer is in a meeting with a village head. She leaves a voice note. At 5:30pm he calls back with the numbers verbally. She writes them down. She enters them. She also needs her director's signature on the cover letter before it can be submitted. Her director is traveling in Surabaya. Ratna sends the letter via email for review at 5pm. The director reviews it and has one comment — a change in the executive summary. Ratna makes the change, re-exports the PDF, and emails it back. The director, now at dinner with a partner organization, says he'll sign in the morning. The report goes out Friday at 9:30am. It is technically on time. Ratna has sent 63 WhatsApp messages, made 14 calls, and transcribed roughly 2,500 words of verbal field data in the last 36 hours. Her two assistants did similar volumes. None of this labor is visible in the report. --- ## Cross-Profile Patterns: What These Five Have in Common ### The accountability-authority gap In every profile, the person doing the coordination does not have full authority over the people and processes they are responsible for. Pak Budi has authority but no system. Sari has authority over her team but not over the approval chain. Dinda has no authority over engineering. Eko has nominal authority but limited enforcement power. Ratna has no authority over cross-institutional processes. The coordination burden falls on whoever cares most, not whoever has the formal power to make things move. ### WhatsApp as the real operating system Across all five profiles, WhatsApp is the actual coordination medium — not the official tool. This is true even in profile 3 (the startup), where Slack is official but WhatsApp is what Sales uses. The official tools capture some work. WhatsApp captures the real-time decisions, the informal agreements, and the human relationships that make work actually happen. ### The invisible labor of chasing All five people spend significant daily time chasing: following up with people who haven't responded, confirming things that should be confirmed by the system but aren't, and manually reconstructing status that should be automatically visible. This labor is unpaid, unrewarded, and invisible — it doesn't show up in any tool, any report, or any performance review. It is entirely absorbed by the coordinator. ### The "yes that isn't yes" problem All five coordinators have adapted their communication practices to the Indonesian cultural norm of indirect response. They have all developed personal correction factors — adding buffer days to timelines, assuming "besok" means "maybe this week," following up voice note agreements with written messages to create a record, and reading silence as a signal rather than as absence. This cognitive adaptation is constant, tiring, and entirely absent from their official workflows. ### Documentation happens after the fact, if at all None of the five have workflows where decisions are documented at the moment they're made. Documentation, when it happens, is reconstructed after the fact by someone who cared enough to write it down — usually the coordinator. The institutional memory of the organization lives in people's WhatsApp chats and personal notes. When people leave, it leaves with them. ### The coordination tax is personal Every profile describes coordination friction being absorbed by an individual body: Pak Budi on the back of an ojek, Sari in an 8pm revision cycle, Dinda in a Thursday afternoon scramble, Eko with a dying phone battery and an inaccurate report, Ratna transcribing handwritten sheets by flashlight. The cost of bad coordination is paid in person. It shows up as stress, late nights, missed family time, and eventually burnout. Indonesian research on Gen Z workplace burnout consistently shows that workload — broadly defined to include coordination overhead — is the primary driver. --- ## What Users Actually Want When asked directly, people in these roles rarely say "I want a better project management tool." They say things like: - "I want to know what's happening without having to ask everyone" - "I want people to just do what they said they'd do" - "I want to be able to trust that the information I have is current" - "I want to stop being the one person who has to remember everything" - "I want to spend time on the actual work, not on coordinating the work" The emotional register is exhaustion, not frustration with software. The problem they feel is not "my tool is bad." The problem they feel is "I am tired of being the system." --- ## Version History | Version | Date | Author | Changes | |---------|------|--------|---------| | 1.0 | June 2026 | Claude (Anthropic) | Initial document — five user profiles with daily context, team size, workflow, frustrations, workarounds, and bad-day scenarios; plus cross-profile synthesis |