How Elena, The Administrative Systems Coordinator, Uses WayOfTeams
A step-by-step walkthrough of how an experienced operations coordinator with zero AI experience moves from skeptical observer to daily power user using WayOfTeams as the bridge between spreadsheets and AI-assisted operations.
Who Elena Is
Elena is an experienced operations coordinator who keeps the business running smoothly. She manages schedules, coordinates vendors, writes client emails, organizes event timelines, and maintains the documentation everyone else forgets about. She is highly skilled in traditional software — Excel, ERP systems, email, and project boards — but she has zero prior experience with AI tools.
She views tech purely through the lens of efficiency, reliability, and ease of use. She does not care how the technology works under the hood. She only cares if it actually saves time without creating errors she has to clean up later.
Her current tool set: standard email clients, spreadsheets, shared documents, calendar systems, and task trackers. She is cautiously open to AI but skeptical. She needs simple, copy-paste workflows or natural text templates that fit directly into her existing daily routine without technical setup.
Phase 1: First Login (Minutes 0–5)
What Elena Does
Someone on her team says "we are using WayOfTeams now." She gets an invite email, clicks the link, signs in with Google, and lands on the dashboard. She sees a dark-themed interface with a sidebar, stats in the middle, and an AI chat panel on the right.
She is nervous. She heard "AI" and imagined a complicated terminal with code. What she sees is a chat box that looks like every messaging app she has ever used.
She types:
"Hi, I am new here. What can you help me with?"
The AI responds in plain language with a list: turn meeting notes into action items, draft emails, organize information into tables, create tickets, set up kanban boards, write and manage documents.
She thinks: "Okay, this is just like ChatGPT but connected to our project."
What Catches Her Attention
The AI chat panel is right there on the dashboard. She does not need to open a separate app or learn a new interface. She can see her team's recent activity — tickets created, standups submitted, work completed — while she chats.
Why This Works for Elena
She tried ChatGPT before. It felt disconnected from her actual work. This AI is inside the same system where her team tracks tasks. It knows the context. It is not a separate tab she has to copy-paste between.
Phase 2: Her First Real Task (Minutes 5–20)
What Elena Does
She has a meeting in 20 minutes. She has rough notes from yesterday's vendor call. Bullet points, half-sentences, action items scattered throughout. She pastes them into the AI chat:
"Here are my notes from yesterday's vendor call. Turn them into a clean summary with action items, who is responsible, and deadlines.
Notes:
- Called Acme Supply about the March shipment
- They said delivery delayed 2 weeks, reason: port congestion
- Need to find backup vendor for critical parts
- Maria said she has a contact at Global Parts
- Follow up with Acme by Friday for updated ETA
- Internal meeting Thursday to decide on backup vendor
- Budget impact: if we switch vendors, costs go up about 15%"
The AI produces a formatted summary:
VENDOR CALL SUMMARY - Acme Supply
Date: [today]
ISSUE: March shipment delayed 2 weeks due to port congestion
ACTION ITEMS:
1. Elena - Follow up with Acme Supply by Friday for updated ETA
2. Elena - Ask Maria for Global Parts contact information
3. Team - Internal meeting Thursday to decide on backup vendor
4. Finance - Assess 15% cost increase if switching vendors
STATUS: Awaiting Acme's updated timeline
She reads it. Every action item has an owner. Every date is correct. She copies it into an email and sends it to her manager. Two minutes instead of fifteen.
She tries the same thing with meeting notes from a different call. This time the AI gets the dates wrong. She says "the meeting was on Tuesday, not Wednesday." The AI fixes it. She learns that she needs to double-check dates and numbers.
What She Notices
- The AI produces clean, professional output from messy input
- She can ask for corrections in plain language
- The output is copy-paste ready for email
- She still reviews everything before sending
Why This Works for Elena
The AI did not ask her to learn prompt engineering. She gave it messy input, got clean output, and moved on with her day. The input and output is predictable and reliable. Exactly what she needs.
Phase 3: Creating Her First Ticket (Day 1–2)
What Elena Does
Her manager says "put that vendor issue in the tracker." She asks the AI:
"Create a ticket for the Acme Supply delivery delay. High priority, assigned to me, due by Friday."
The AI creates the ticket with title, priority, assignee, due date, and status. She sees it appear on the kanban board as a card she can move across columns.
She creates three more tickets that afternoon. One for the vendor follow-up. One for the Q2 planning meeting logistics. One for updating the vendor contact spreadsheet. Each one takes 30 seconds to describe and the AI structures the rest.
What She Notices
- Tickets are just descriptions of work — problem, outcome, who, when
- The AI creates them from natural language. No forms to fill out.
- The kanban board shows all her team's work in one place
- She can drag cards to change status. No dropdown menus.
- The ticket links to her name. She can see all her work in one view.
Why This Works for Elena
She used Jira and Asana. They required 10 fields to create a task. WayOfTeams lets her describe the work in English and the AI structures it for her. Less clicking, more doing.
Phase 4: The Kanban Board (Day 2–3)
What Elena Does
She opens the Kanban page and sees her team's board with columns: Backlog, In Progress, Review, Done. Her Acme Supply ticket is in In Progress. She drags it to Review after sending the follow-up email. The ticket status updates automatically.
She creates a private board (scope: private) for her own tasks:
- Email follow-ups due this week
- Event logistics for Q2 planning meeting
- Vendor contact list update
Nobody else sees her private board. It is her personal task tracker.
She uses board view for drag and drop, calendar view for deadlines, list view for filtering and searching, and the Today view for what is due now. She attaches files to cards — a spreadsheet with vendor pricing, a PDF with the shipment contract, a screenshot of the delay notification. The system extracts text from PDFs and documents, making them searchable.
She discovers the list view is her favorite. She can filter by assignee (show only her tickets), by status (show only In Progress), or by priority (show only High). She types "Acme" in the search box and instantly finds every ticket related to the Acme Supply situation.
What She Notices
- Board view: drag-and-drop cards between columns
- Calendar view: deadlines on a shared calendar
- List view: filter and search all tickets
- Today view: what is due today, what needs attention
- Private boards: invisible to everyone except her
- File attachments: documents linked to tasks, searchable
Why This Works for Elena
She tracked tasks in spreadsheets. The kanban board is like a spreadsheet that moves itself. She drags a card, the status updates, the dashboard updates, the standup updates. No manual status columns to maintain.
Phase 5: Drafting Emails and Documents (Day 3–5)
What Elena Does
She has a stack of emails to write. She opens the AI chat:
"Draft a professional email to Global Parts asking about their availability for emergency orders. We need industrial valves, model XV-200, quantity 500, within 3 weeks. Keep it formal but friendly."
The AI produces a polished email. She reads it, makes two tweaks, and sends it. Five minutes instead of twenty.
She tries more scenarios:
Vendor comparison: She pastes pricing data from three vendors and asks the AI to create a comparison table. The AI formats it with columns for vendor name, product, unit price, minimum order, lead time, and payment terms. She pastes it into a document and shares it with her manager.
Meeting agenda: She lists six topics in no particular order. The AI groups them into logical sections, adds time estimates, and suggests who should present each topic.
Status report: She gives the AI bullet points about what her team did this week. The AI writes three paragraphs in professional prose.
Client update: She describes a shipping delay in plain terms. The AI rewrites it as a formal client notification with appropriate tone and next steps.
The AI remembers context from earlier in the conversation. When she says "make it shorter" or "add the deadline," it knows what she means.
What She Notices
- The AI produces professional output from rough input
- She can ask for tone adjustments: "make it more formal"
- Context carries over in the conversation
- She still reviews everything before sending
Why This Works for Elena
She spends 40% of her day writing emails and documents. The AI cuts that to 15%. It gets her 80% of the way there in seconds. She still reviews everything, but the draft is already clean.
Phase 6: Organizing Data into Tables (Week 2)
What Elena Does
She has a messy list of vendor contacts someone pasted into a shared doc. Names, emails, phone numbers, product categories — all jumbled.
She pastes it into the AI chat:
"Organize this into a table with columns: Vendor Name, Contact Person, Email, Phone, Product Category, Last Contact Date"
The AI produces a clean table. She copies it into a spreadsheet.
She does the same with event attendee lists, budget line items, project timelines, and inventory counts. The AI handles messy input gracefully. The output is copy-paste ready for Excel, Google Sheets, or email.
What She Notices
- The AI handles messy input gracefully
- She can ask for specific formats: tables, lists, timelines
- The output is in the format she needs, not a format she has to fix
- She does not need to learn any new tools
Why This Works for Elena
She spent hours cleaning up data in Excel. The AI does in seconds what used to take an afternoon. The output is in the format she needs.
Phase 7: Standups Without the Meeting (Week 2–3)
What Elena Does
Her team has a daily standup meeting at 9 AM. She dreads it. The same 15 minutes every day of people reading their status updates from notes they scrambled to write at 8:55.
She discovers the Standups page. The AI generates her standup automatically from her recent activity: tickets she moved, emails she drafted, work she completed.
YESTERDAY:
- Followed up with Acme Supply on delivery ETA
- Drafted email to Global Parts for emergency valve order
- Updated vendor comparison spreadsheet
- Moved Q2 planning ticket to In Progress
TODAY:
- Waiting for Acme's response (due Friday)
- Prepare agenda for Thursday's backup vendor meeting
- Send Q2 planning meeting invites
BLOCKERS:
- Acme has not responded yet, may need to escalate
She reviews it. Everything is accurate. She makes one small edit and submits it. The meeting is canceled because everyone submitted standups online.
By the end of the second week, the daily meeting is gone. 15 minutes a day times 5 days a week equals five hours a month saved. Across a team of eight, that is 40 hours a month of meeting time eliminated.
What She Notices
- The standup is auto-generated from her actual work
- She reviews and submits in 2 minutes
- The daily meeting is eliminated
- Her manager sees all standups in one view
Why This Works for Elena
She does not like meetings that could be emails. The standup system replaces the daily meeting with a 2-minute review of an auto-generated summary. She spends her morning on work, not in a conference room.
Phase 8: Team Chat and Collaboration (Week 3)
What Elena Does
She opens Team Chat. It looks like Slack or Teams. She messages her teammate:
"Maria, what is that Global Parts contact's name again?"
Maria responds. They discuss the vendor situation back and forth. The AI captures their conversation and creates a ticket:
- Title: "Evaluate Global Parts as backup vendor"
- Linked to: The Acme Supply delay ticket
Elena did not ask the AI to create the ticket. It recognized that the conversation was about a decision that needed tracking.
The meeting notes from Thursday's backup vendor discussion are captured automatically. The AI extracts action items and turns them into sub-tasks on the ticket.
What She Notices
- Real-time messaging without email chains
- Video calls built in, no separate Zoom link
- AI captures decisions from conversations
- Tickets created from chat messages automatically
- Everything is searchable
Why This Works for Elena
She used to switch between email, Teams, and the project board. WayOfTeams puts messaging, video calls, and task management in one place. The AI bridges the gap between talking and doing.
Phase 9: Ideas and Improvements (Week 3–4)
What Elena Does
She has ideas about improving vendor management. She goes to the Ideas page and submits:
"Create a shared vendor scorecard that tracks delivery reliability, quality, and responsiveness. Update it monthly."
She upvotes her own idea. Her manager sees it and upvotes too. The idea moves to Under Review. When approved, the AI creates a ticket and a plan. She reviews the plan and says "start with step 1."
What She Notices
- Ideas are tracked, not lost in email
- Voting helps prioritize
- Approved ideas become tickets automatically
- She can see the status of her suggestions
Why This Works for Elena
She always had ideas about process improvements. Before, she emailed them and hoped they were not forgotten. Now they are in a system with voting, status tracking, and automatic ticket creation.
Phase 10: The Routine That Sticks (Month 2+)
What Elena Does
Elena has a daily rhythm now:
Morning (5 minutes): Open dashboard, check Today view, review auto-generated standup, submit it, check notifications. She glances at the kanban board to see what moved overnight.
During the day: Use AI chat to draft emails, format data, summarize meetings. Drag kanban cards as work progresses. Attach documents to cards for team visibility. Send quick messages in Team Chat instead of email. When she gets a phone call from a vendor, she jots notes and asks the AI to turn them into a summary before she forgets.
End of day: Check what moved to Done. She likes seeing the Done column grow. Submit standup. Review tomorrow's calendar view.
Weekly: Review Ideas page for process improvement suggestions from her team. Check team notifications for anything she missed. Look at the dashboard stats to see team progress.
She does not think about "using AI." She thinks about getting her work done. The AI is just part of how she does it now.
Feature Adoption Order
Based on Elena's profile, here is what she uses and when:
| Priority | Feature | Why Elena Cares |
|---|---|---|
| 1 | AI Chat | Familiar chat interface, immediate value |
| 2 | Ticket creation | Describe work in English, AI structures it |
| 3 | Kanban board | Visual task tracking, drag and drop |
| 4 | Email and document drafting | 80% of her day, massive time savings |
| 5 | Data organization | Tables, lists, timelines from messy input |
| 6 | Standups | Auto-generated, no meeting needed |
| 7 | Team Chat | Familiar messaging, AI captures decisions |
| 8 | Ideas | Process improvements with voting |
| 9 | File attachments | Documents linked to tasks |
| 10 | Calendar view | Deadlines on a shared calendar |
| 11 | Memory | AI remembers context across sessions |
| 12 | Private boards | Personal task tracking, invisible to others |
What Makes WayOfTeams Different for Elena
| Problem Elena Has | WayOfTeams Solution |
|---|---|
| "I do not know how to talk to AI" | Plain language input, predictable output, no prompt engineering |
| "AI gives wrong dates or inaccurate info" | Structured tickets force accurate data, she reviews everything |
| "AI feels disconnected from my work" | AI is inside the same system as tasks, kanban, and team chat |
| "I waste time on emails and formatting" | AI drafts emails, formats tables, structures documents in seconds |
| "Meetings could be emails" | Auto-generated standups replace daily meetings |
| "My ideas get lost" | Ideas page with voting, status tracking, ticket creation |
| "I use 5 different tools" | Tasks, chat, docs, kanban, and AI in one place |
| "I cannot track what my team is doing" | Dashboard shows all team activity, tickets, and standups |
The Core Loop
For Elena, WayOfTeams boils down to one simple daily cycle:
Capture -> Draft -> Track -> Collaborate -> Review -> Repeat
^ |
+---------------------------------------------------+
Every iteration builds momentum:
- Capture turns messy notes into structured summaries
- Draft produces polished emails and documents in seconds
- Track keeps work visible on kanban boards and tickets
- Collaborate replaces email chains with real-time chat
- Review generates standups and activity summaries automatically
- Repeat because the system remembers context across sessions
The loop runs through a chat interface she already understands, a kanban board that updates itself, and an AI that learns her workflow.
That is the system Elena would actually use every day.