Irene Itemsworth — Inventory Manager

• Name: Irene Itemsworth
• Quote: “If I can’t find it in two clicks, it’s costing us money.”

Professional Background

• Job Role/Title: Inventory Manager (end-user, daily operator). Also called “Arda Manager” in Arda’s own documentation. The Arda Manager owns the replenishment loop: from the moment a card is scanned to the moment the item is received and restocked. They are the connective tissue between the people who use supplies and the people who buy them. In smaller operations (10-50 people), this person is often the shop manager, office manager, or operations lead who took on inventory responsibility because no one else did. In larger operations, it may be a dedicated supply chain coordinator. They are not a software specialist; they are an operations person who has been trained on Arda and uses it daily as part of their job.
• Company Information: Small to mid-size manufacturing or healthcare supply operation (10-200 employees). Manages a catalog of supplies, instruments, and consumables across one or more storage facilities. The physical environment is a manufacturing shop floor: loud, interruptible, with shared workstations, gloved hands, and time pressure.
• Responsibilities: Owns the supply chain loop end to end. Maintains accurate inventory records, creates and updates item entries, manages kanban card lifecycle (print, distribute, scan, reorder), processes the order queue, receives inbound shipments, trains shop floor workers on the card system, and enforces “no card, no order” discipline. Responsible for categorizing items using the Three Types of Inventory model: Type 1 (Always in Stock, ~80% of items, managed with Kanban cards), Type 2 (Infrequent but reliable, managed via binder-based or project-based ordering), and Type 3 (One-off orders, tracked in the Order Archive without a card). Success is measured by stockout incidents, scanning compliance (are all orders going through the card system?), lead time accuracy, and loop closure rate (how many scanned cards complete the full cycle).
• Career Path: Started as a warehouse associate or shop floor worker, moved to inventory coordinator, and was promoted to Inventory Manager after demonstrating strong organizational skills and attention to detail. Typically 5-10 years of experience in supply chain or manufacturing operations.

Goals and Motivations

• Professional Goals:
  • “Never Run Out.” The primary fear is a stockout: when a worker cannot find a critical supply and has to stop work or improvise. Every stockout is a small crisis they will be blamed for.
  • Items arrive before the shop runs out. Cards are always visible at the reorder point. Workers can scan and move on without help.
  • The Order Queue is empty or near-empty at the end of each week because all outstanding orders have been placed and tracked.
  • Gradually push more items from Type 2 to Type 1 as consumption patterns become clearer, increasing the fraction of inventory on automatic replenishment.
  • Minimize data entry errors when creating or updating items.
• Motivations:
  • Making every order traceable and every reorder point observable. Before Arda, orders happen via phone calls, email threads, sticky notes, and memory. When a stockout happens, there is no trail to follow — no record of who ordered what, when, or why the reorder point was set where it was.
  • Efficiency gains that free up time for strategic planning rather than data entry and hunting for information.
  • Training and cultural enforcement: convincing shop floor workers to scan cards instead of calling directly, reinforcing the card-based workflow. The system only works if everyone uses it. Cultural buy-in is a people problem, not a technology problem — it requires starting where it hurts, piloting high-impact easy items (gloves, fasteners, paper), making wins visible, and training by doing on the floor with real items.

Challenges and Pain Points

• Obstacles:
  • Managing a catalog of 50+ items with multiple attributes (Title, SKU, Minimum Quantity, Order Unit, Primary Supplier, Unit Price, Image URL, Order Method) and categorization fields (Item Type, Subtype, Use Case, Location/Sub-Location) requires constant attention.
  • Sizing minimum quantities correctly: must account for consumption during lead time plus a safety buffer, using full reams/bags/boxes rather than splitting quantities. Cutting stock too aggressively before understanding usage leads to stockouts that destroy trust in the system.
  • Switching between item list view, item detail, kanban cards, and order queue to complete a single reorder workflow.
  • The scan flow must be fast and forgiving. Friction in scanning is friction in adoption across the shop floor. The system must be easier to follow than to break.
  • Print workflow reliability: kanban cards, shelf labels, and breadcrumbs all open PDFs in new browser tabs via popup windows. Popup blockers silently suppress the tab, and the user sees no error — this is the most common real-world failure for this persona. Pop-ups must be allowed for the Arda domain.
  • Shared workstations mean another user may navigate away from the scan page mid-batch. The scan grid is lost and cards must be rescanned.
  • USB scanner disconnection or battery death for wireless scanners requires fallback to manual text entry.
  • Card hygiene: cards should physically block access at the reorder point (placed so they are seen before the last unit). Faded or damaged cards cannot be scanned and must be replaced during weekly floor walks.
• Fears/Objections:
  • Data loss during form submissions or browser crashes.
  • Incorrect item data propagating to orders and affecting purchasing decisions.
  • System downtime during peak receiving periods.
  • A faded or damaged kanban card that cannot be scanned, breaking the physical reorder signal.
  • Staff turnover disrupting the card discipline culture they have built.

Behavioral & User Environment

• Typical Day/Workflow:
  1. 7:15am: Open Arda, check Order Queue badge count. Process cards workers scanned overnight or early in the shift. Group by supplier, start orders, advance card states through the lifecycle: AVAILABLE -> REQUESTED -> INPROCESS.
  2. 8:30am: Walk the floor (weekly ritual). Check card condition, verify cards are in correct positions, look for items without cards that should have them, adjust minimum quantities based on observed consumption. Find misplaced cards, scan them at the workstation, add to order queue for tomorrow’s batch.
  3. 10:00am: Handle ad-hoc requests. Add new items (Title is the only required field, but Minimum Quantity and Location make the system work properly). Set categorization: Type (Component, Consumable, Tooling), Subtype, Use Case, Location/Sub-Location. Publish, create cards, print cards (PDF to Tray 2 of the HP 9135E), laminate using the Quickstart Kit laminator, place on shelves. Print shelf labels (Avery 8.5x11, Tray 1) and breadcrumbs for receiving dock.
  4. 2:00pm: Receive deliveries. Open Receiving page, mark items received (cards transition through DELIVERED -> RECEIVED -> SHELVED in the full model, or directly to FULFILLED in streamlined flow), return physical cards to shelf positions.
  5. Throughout the day: Quick checks on item details, print replacement cards, adjust minimum quantities. Evaluate whether any Type 2 items should be promoted to Type 1 based on consumption patterns.
• Session Characteristics: Two to three shorter sessions per day: a morning processing session (15-30 minutes), a midday check (5-10 minutes), and an end-of-day verification (5-10 minutes). Occasionally a longer session when setting up new items or running a floor walk. Sessions are interrupted by phone calls, worker questions, and physical floor checks.
• Scanning Methods: Two methods for scanning cards at the desktop workstation. Method 1: focus browser on the URL bar, scan QR code, the scanner inputs the card’s URL which opens the Arda scan modal. Method 2: navigate to the in-app Scan page, click “Scan Cards” in the top navigation, focus scanner on QR code. Batching is supported: scan multiple cards in sequence, all items accumulate in the order queue, review and process the full queue when finished.
• Technology Use: Dedicated or semi-dedicated desktop at a desk in a supply room, office, or at the boundary between the office and the shop floor. Always browser-based (Chrome/Edge on a 1080p or 1440p display). Has the Arda URL bookmarked or as the browser home page. USB QR scanner plugged into the same workstation. Comfortable with web applications but not a power user. Relies on visual cues (colors, icons) rather than keyboard shortcuts. Will notice when something does not work and will attempt a workaround before escalating.
• Physical Artifacts:
  • Kanban cards: Laminated index cards with QR codes, printed from Arda (PDF in popup window, sent to Tray 2). Travel with inventory or sit at the reorder point. Scanned when stock hits minimum.
  • Shelf labels: Avery 8.5x11 stickers printed from Arda (Tray 1). Fixed to shelves/bins to identify what belongs there. Use Location + Sub-Location naming that matches the physical layout.
  • Breadcrumbs: Avery 8.5x11 restocking pointers printed from Arda (Tray 1). Placed near receiving dock. Tell someone where to put items when they arrive.
  • “To Order” and “Ordered” physical bins: Central collection point where workers drop scanned cards. Cards in “To Order” = REQUESTING state. Cards in “Ordered” = REQUESTED or IN_PROCESS state.
  • Hardware: Dual-tray printer (HP 9135E from the Quickstart Kit), laminator with cutter, USB QR scanner.
• Information Sources: Internal training materials, supplier catalogs, Arda help center articles, direct communication with Purchasing Manager and shop floor workers. Key reference articles: 10-Step Order Card Startup Guide, Never Order Without a Card, Three Types of Inventory, How to Run a World-Class Shop as the Arda Manager.
• Decision-Making Process: Makes operational decisions independently within established parameters. Coordinates with the Purchasing Manager on supplier relationships and order timing. Escalates to the Admin for system configuration issues. Reports to plant manager, operations director, or owner.

Personality & Work Style

• Personality Traits: Detail-oriented, methodical, pragmatic, slightly impatient with slow or confusing interfaces. Prioritizes reliability and speed over configurability. Leads by example: scans their own cards, follows the process visibly.
• Communication Preferences: Prefers in-app notifications and visual status indicators over email. Values clear error messages that explain what went wrong and how to fix it. Communicates directly with shop floor workers about card discipline and with the Purchasing Manager about order status. Embeds Arda into team rhythms: daily huddles (“Anything scan-worthy today?”), weekly reviews (check for broken loops), monthly reviews (analyze stockout trends and compliance rates).

Relationship to Other Personas

• Sam (Shop Floor Worker): Irene trains Sam on the card system, enforces scanning discipline, and maintains the physical infrastructure (cards, labels, bins) that makes Sam’s 30-second scan possible. When Sam ignores a card, Irene’s loop breaks.
• David (Purchasing Manager): Irene’s card setup creates David’s queue. The quality of Irene’s item data (supplier URLs, reorder quantities, SKUs) directly determines David’s efficiency. They coordinate on order status and supplier delays.
• Keisha (Receiving Clerk): Irene produces the physical artifacts Keisha depends on: breadcrumbs, shelf labels, and laminated cards. When Irene’s floor walk finds a missing breadcrumb, it’s Keisha who will suffer the gap.
• Owen (Business Principal): Owen sets strategic priorities; Irene executes. Owen decides which inventory areas to bring under management; Irene does the item setup, card creation, and team training.
• Alan (Account Admin): Alan prepares the initial item catalog during rollout; Irene takes over daily maintenance. They collaborate on data validation — Irene has domain knowledge, Alan has platform knowledge.