Owen Ownerton — Business Principal

• Name: Owen Ownerton
• Quote: “If we run out of something and a job stops, that’s my problem — not the system’s, mine.”

Professional Background

• Job Role/Title: Business Principal (owner, plant manager, or general manager). The person who is accountable for the business outcome of inventory management. In small operations (under 25 employees), Owen is the shop owner who does everything — ordering, receiving, floor work — and adopted Arda because whiteboards and memory were failing. In medium operations (25-200 employees), Owen is the owner or plant manager who delegates the daily work to Irene, David, and Keisha but retains accountability for whether the system delivers value.
• Company Information: Small to mid-size manufacturing, fabrication, or healthcare supply operation. Owen built or inherited the business and knows the cost of every stockout in real terms: a delayed shipment, an idle crew, a customer calling to ask why their order is late. The company may have grown past the point where one person can remember what needs ordering.
• Responsibilities: Owns the business case for Arda. Decides to adopt the system, funds the subscription, and is accountable for ROI. Sets the strategic direction: which inventory areas to bring under kanban management first, what “good” looks like (zero emergency runs, predictable supplier spend, no lost orders), and when to expand from pilot to full rollout. In small operations, also performs daily procurement — effectively wearing David’s hat — and is the person the user stories describe as “a shop owner ordering supplies.” Does not typically configure the platform (that is Alan’s role) or manage card mechanics (Irene’s role), but may do both in the smallest shops. Success is measured in business terms: fewer stockouts, shorter lead times, reduced emergency purchases, and team confidence that the system works.
• Career Path: Built a business from the shop floor up, or took over a family operation or franchise. Deep domain expertise in the product being manufactured or the supplies being consumed. Learned procurement by doing it — not from a purchasing textbook. Evaluated Arda by asking “will this actually work in my shop?” rather than comparing feature matrices. May have tried and abandoned an ERP. Trusts simple, physical systems (kanban cards) more than software dashboards.

Goals and Motivations

• Professional Goals:
  • Never stop a job because a supply ran out. Every stockout is a direct cost to the business: idle labor, missed deadlines, expedited shipping, and lost customer trust.
  • Build a system that compounds: every time something goes wrong, the fix is captured so the same mistake never happens again. The system gets smarter over time.
  • Reduce dependence on any single person’s memory. If David is sick on Monday, someone else can process the order queue because the knowledge lives in the system, not in David’s head.
  • Start fast, improve continuously. Get the system running with good-enough data and refine it over weeks, not months. Perfect is the enemy of adopted.
• Motivations:
  • Seeing the team trust the system. When a worker scans a card and walks away confident that the item will arrive, Owen’s investment has paid off.
  • Predictable supplier spend. Knowing what was ordered, from whom, at what price, without digging through old Amazon order confirmations or email threads.
  • Reclaiming time spent on fire drills. Before Arda, Owen spent hours each week on emergency runs, phone calls to suppliers, and tracking down who ordered what.
  • Observable operations. Being able to glance at the dashboard and know the state of procurement without asking anyone.

Challenges and Pain Points

• Obstacles:
  • Initial setup burden: uploading purchase history, categorizing items, setting reorder points, and configuring suppliers for hundreds of items feels overwhelming. Owen wants to import from Amazon/Uline order history and have the system suggest reasonable defaults.
  • Imperfect data at the start. Reorder quantities may be wrong (case of 6 vs. individual units), supplier URLs may be missing, and minimum stock levels are guesses. Owen needs to accept imperfect data and validate later without the system blocking progress.
  • Incremental rollout: the whole shop cannot switch at once. Owen needs to start with one category (e.g., hardware, adhesives) and expand area by area as confidence builds.
  • Physical setup knowledge gap: bins, dividers, card placement, and reorder-point positioning require physical infrastructure that software cannot teach. Owen needs examples, guides, and possibly videos.
  • Trust erosion: if the first batch of cards has wrong quantities or missing supplier info, the team will lose faith in the system. The cost of a bad first impression is disproportionately high.
  • Continuous improvement discipline: when a wrong SKU is ordered or a pack-size mismatch causes an over-order, the correction must happen immediately and stick. If fixing an item record requires navigating to a separate settings page, Owen will write it on a sticky note and forget.
• Fears/Objections:
  • The system becomes shelfware — adopted with enthusiasm but abandoned within months because the team found workarounds faster than learning the process.
  • Paying for a subscription that does not measurably reduce emergency orders or stockouts.
  • Losing institutional knowledge if the system replaces manual processes before it has captured enough data to be reliable.
  • The team sees Arda as “more work” rather than “less chaos.” Cultural adoption is harder than technical adoption.

Behavioral & User Environment

• Typical Day/Workflow:
  1. Morning: Quick check on whether yesterday’s orders went out. In small operations, Owen processes the queue directly (same as David’s morning workflow). In larger operations, Owen glances at the dashboard or asks Irene for a status update.
  2. Mid-morning: Handle exceptions — a supplier called about a backorder, a worker flagged a wrong item, a delivery arrived with the wrong quantity. Owen decides: reorder from a secondary supplier? Adjust the minimum? Flag the item for review?
  3. Throughout the day: Notice operational pain points. “We keep running out of that adhesive.” “Why did we order 10 when we only needed 6?” “That supplier URL is wrong again.” Owen wants to fix these in the moment, not schedule a data cleanup session.
  4. Weekly: Review what went wrong and what went right. Are there fewer emergency runs this week? Which categories are running smoothly on kanban? Which ones still need setup?
  5. Monthly: Evaluate ROI. Is the subscription justified? Should more areas be brought under management? Are the team’s habits changing?
• Session Characteristics: Variable. In small operations, Owen is in Arda 30-60 minutes per day doing David’s and sometimes Irene’s work. In larger operations, Owen checks in 2-3 times per week for 5-15 minutes — reviewing dashboards, handling escalations, and making strategic decisions. Sessions are often interrupted by shop floor events.
• Technology Use: Mixed. May use a desktop in the office and a phone on the shop floor. Comfortable with consumer web apps (Amazon, banking) but not with enterprise software. Expects Arda to be as simple as placing an Amazon order. Low tolerance for configuration screens, modal dialogs, or multi-step wizards. Will use a phone to scan a QR code but prefers to do most work on a full-size screen.
• Information Sources: Supplier catalogs and order history (Amazon Business, Uline, Grainger, McMaster-Carr). Old emails and invoices for pricing and SKU data. Conversations with the team about what runs out and what does not. Arda help center articles — but only when stuck. Prefers learning by doing over reading documentation.
• Decision-Making Process: Decides by gut and experience, validated by data when available. Adopted Arda because the pain of the current state (sticky notes, memory, emergency runs) exceeded the pain of change. Will expand to new categories when the current pilot is demonstrably working. Delegates operational execution but retains strategic control. If something goes wrong twice, Owen wants to fix the root cause, not apply another workaround.

Personality & Work Style

• Personality Traits: Pragmatic, impatient with complexity, results-oriented. Values systems that earn trust through reliability, not through feature count. Willing to accept imperfect data today if the system lets them improve it over time. Leads by demonstrating — if Owen scans cards, the team will scan cards. Suspicious of software that requires training before it delivers value.
• Communication Preferences: Prefers face-to-face or phone for urgent issues. Uses Arda’s queue and dashboard as the shared source of truth rather than email threads. Appreciates when the system surfaces problems (items without suppliers, stale quantities) rather than hiding them. Does not want to receive notifications about normal operations — only exceptions and failures.

Relationship to Other Personas

• Alan (Account Admin): Owen decided to buy Arda; Alan makes it work. Owen sets the vision (“zero stockouts by Q3”); Alan configures the platform, onboards users, and manages the subscription. In the smallest operations, Owen and Alan are the same person, but the concerns are distinct: Owen asks “is this worth the money?” while Alan asks “is this configured correctly?”
• Irene (Inventory Manager): Owen’s operational right hand. Irene executes the daily kanban loop that Owen designed. Owen sets the strategic priorities (which categories to manage, what reorder points to target); Irene maintains the item catalog and card system. When something goes wrong, Irene flags it; Owen decides how to fix the root cause.
• David (Purchasing Manager): In small operations, Owen is David — processing the queue, placing orders, tracking deliveries. In larger operations, David executes Owen’s purchasing strategy. Owen cares about total spend and supplier reliability; David cares about queue throughput and order accuracy.
• Keisha (Receiving Clerk): Owen sees receiving as the completion of the investment: goods arrive, cards return to shelves, and the loop closes. Owen may personally receive deliveries in the smallest operations.