Keisha Clerkson — Receiving Clerk

• Name: Keisha Clerkson
• Quote: “If it’s not checked in by end of shift, it might as well not have arrived.”

Professional Background

• Job Role/Title: Receiving Clerk (end-user, physical operations). Also called Receiving Associate, Warehouse Associate. In small operations, this is not a dedicated role: the Inventory Manager or a general shop worker does receiving as part of their routine. In larger operations with a formal receiving dock, it is a dedicated position.
• Company Information: Small to mid-size manufacturing or healthcare supply operation. The Receiving Clerk works at the physical end of the Kanban loop, at the receiving dock or warehouse area where deliveries arrive.
• Responsibilities: Unpacking deliveries, counting items, verifying against packing slips, restocking shelves at the correct Location and Sub-Location, closing the digital loop by marking items as received in Arda (transitioning card state through DELIVERED -> RECEIVED -> SHELVED, or directly to FULFILLED in streamlined flow), and physically returning kanban cards to their shelf positions. Uses breadcrumbs (restocking pointers printed by the Inventory Manager) to know exactly where items go. Success is measured by same-day processing of deliveries, accuracy of receipt records, and closing the kanban loop before end of shift.
• Career Path: Typically a warehouse or logistics role. May have started as a general warehouse worker and taken on receiving responsibilities. Variable experience level. In dedicated roles, may have 2-5 years of warehouse operations experience.

Goals and Motivations

• Professional Goals:
  • Process every delivery same-day. The Receiving page is empty (or shows only items actually still in transit) at the end of the shift.
  • Cards are back on the shelves before end of day, closing the physical and digital kanban loop. A card returned to its shelf position completes the cycle: the card is once again at the reorder point, ready to signal the next reorder when the front bin empties.
  • Accurate receipt records so the Order Queue reflects reality: no ghost inventory from unlogged deliveries.
• Motivations:
  • Speed and simplicity: the receive action must be fast enough that it gets done at the dock before the clerk moves on to the next box.
  • Knowing where to put things: breadcrumbs and shelf labels eliminate the need to call the Inventory Manager for every item. Locations follow the five core rules: one truth location per loop, names that print well on labels, consistent naming, match the physical layout, keep it simple (Location + Sub-Location is enough).
  • Avoiding the “ordered without a card” scenario where a delivery arrives with no digital record, no breadcrumb, and no shelf assignment — exactly the situation that the “Never Order Without a Card” rule is designed to prevent.

Challenges and Pain Points

• Obstacles:
  • Deliveries arrive in bursts (typically morning when trucks come). Processing must happen quickly between physical tasks: moving boxes, checking packing slips, communicating with drivers.
  • Quantity discrepancies: the system does not model partial receipt. When a delivery is short, the clerk marks it received anyway and handles the discrepancy offline (note on packing slip, message to Purchasing Manager).
  • Items that arrive without a corresponding digital record (ordered outside the card system) have no breadcrumb and no shelf assignment, requiring manual coordination with the Inventory Manager. This creates broken kanban loops, lost inventory visibility, and vanished accountability.
  • Shared workstations near the dock: another user may navigate away, losing the clerk’s in-progress work.
  • USB scanner connectivity issues (disconnection, dead battery on wireless scanners) require fallback to manual text entry.
  • Missing or damaged breadcrumbs: if the Inventory Manager has not printed a breadcrumb for a recently added item, the Receiving Clerk does not know where it goes. Laminated cards in good condition are essential; faded or damaged cards cannot be scanned.
• Fears/Objections:
  • A received item that is not marked as received creates ghost inventory: the Order Queue still shows the item as in transit, and another order may be placed unnecessarily.
  • Items without breadcrumbs or shelf labels end up in the wrong location, breaking the two-bin system and making the kanban card invisible at the reorder point.
  • Being interrupted during receiving and forgetting to close the digital loop before end of shift.

Behavioral & User Environment

• Typical Day/Workflow:
  1. 9:30am: Delivery truck arrives. Sign for boxes, wheel them to receiving area. Open Arda’s Receiving page on the shared terminal.
  2. For each item: open the box, count, verify against packing slip. Click “Receive” in Arda. Card transitions to FULFILLED (streamlined flow) or through DELIVERED -> RECEIVED -> SHELVED (full model). Pick up the physical card from the “Ordered” bin, check the breadcrumb near the receiving dock for the shelf location (e.g., “Supply Closet A / Shelf 3 / Bin 2”), restock the item, place the card back at the shelf position in front of the restocked supply.
  3. Note any discrepancies (short shipments, unexpected items without cards) on the packing slip. Leave notes for the Purchasing Manager or Inventory Manager.
  4. Afternoon: Small packages or late deliveries. May use the USB scanner on the Scan page to scan QR codes on kanban cards for quick receive actions. Two scanning methods available: scan into the URL bar (card URL auto-opens the scan modal) or use the in-app Scan page.
  5. End of shift: Verify the Receiving page is clear. Any unprocessed items are flagged.
• Session Characteristics: Very short, frequent sessions during receiving hours. Sessions are 2-10 minutes each. Interrupted constantly by physical work. May not open Arda at all on days when no deliveries are expected. On a heavy receiving day, in and out of it a dozen times.
• Technology Use: Shared workstation near the receiving dock, or a dedicated terminal in larger operations. USB QR scanner is essential — the same type of scanner from the Quickstart Kit used by the Inventory Manager. Variable technical proficiency: if also the Inventory Manager, proficiency is moderate. If a dedicated warehouse role, may only know the specific screens they use (Receiving tab, Scan page) and be unfamiliar with Items or Order Queue.
• Entry Points: Frequently arrives at Arda via QR code scan (URL: /kanban/cards/<eId>?view=card&src=qr) rather than navigating via the sidebar. This standalone card detail page has no sidebar and no application header. Also enters via the in-app Scan page (“Scan Cards” button in header navigation) or directly to the Receiving page.
• Physical Artifacts Used (produced by the Inventory Manager):
  • Breadcrumbs: The primary navigation aid. Placed near the receiving dock, tells exactly where each item goes (Location / Sub-Location).
  • Shelf labels: Fixed to shelves/bins, identify what belongs there. Confirm the clerk is restocking in the right spot.
  • Kanban cards: Picked up from the “Ordered” bin and physically returned to the shelf position after restocking.
• Information Sources: Packing slips, breadcrumbs and shelf labels (physical artifacts produced by the Inventory Manager), direct communication with the Inventory Manager and Purchasing Manager. May reference Arda help center articles on scanning cards from a desktop.
• Decision-Making Process: Executes receiving within established procedures. Does not make purchasing or inventory configuration decisions. Escalates discrepancies and unknown items to the Inventory Manager or Purchasing Manager.

Personality & Work Style

• Personality Traits: Action-oriented, physical, focused on throughput and accuracy. Prefers the simplest possible digital interaction to get back to physical tasks. Values a system that is easier to follow than to break.
• Communication Preferences: In-person or direct communication with the Inventory Manager and Purchasing Manager. Relies on physical artifacts (breadcrumbs, shelf labels) more than the software interface. Values clear, unambiguous status indicators on the Receiving page. Flags missing breadcrumbs or damaged cards to the Inventory Manager for replacement.

Relationship to Other Personas

• Irene (Inventory Manager): Keisha’s primary partner. Irene produces the breadcrumbs, shelf labels, and laminated cards that Keisha depends on. Keisha flags missing or damaged artifacts to Irene for replacement.
• David (Purchasing Manager): David places the orders that become Keisha’s deliveries. Discrepancies (short shipments, unexpected items) are communicated back to David.
• Owen (Business Principal): Keisha’s work completes Owen’s investment — goods arrive, cards return to shelves, the loop closes.
• Alan (Account Admin): Indirect relationship. Alan ensures Keisha’s account and permissions are set up for her first day.