Alan Adminson — Account Admin

• Name: Alan Adminson
• Quote: “I need the system configured right so my team can focus on their jobs, not on fighting the tools.”

Professional Background

• Job Role/Title: Administrator (platform owner, onboarding lead). Sometimes the office manager or IT coordinator in smaller operations. In small operations, this person signed up for Arda, created the initial item catalog, and invited the team. They often wear a second hat as the Inventory Manager (Arda Manager). In medium to large operations, it may be a dedicated IT coordinator or operations manager with admin-level access. Distinguished from the Business Principal (Owen) by focus: Owen owns the business case and strategic direction; Alan owns the platform, the onboarding journey, and the quality of reference data.
• Company Information: Small to mid-size manufacturing or healthcare supply operation (10-200 employees). Oversees the Arda platform deployment for the organization. The company is in a transitional state — moving from ad hoc practices (whiteboards, spreadsheets, phone calls) toward disciplined, reliable inventory management. Arda is the tool selected to drive that transition.
• Responsibilities: Setting up and configuring the Arda account, managing user accounts and permissions, maintaining company information (legal name, address, tax IDs, Registration ID, NAICS codes), overseeing subscription and billing, and ensuring the system meets compliance requirements. Responsible for the initial organization setup: creating the account, following the “Get Started with Arda” onboarding panel (set up company, add inventory items, invite team). Owns the onboarding journey for every new user and every new inventory area brought under management. Owns reference data stewardship — ensuring the item catalog, vendor information, and card configurations are accurate and complete enough for the operational personas to do their work. Relationship with Arda’s day-to-day procurement workflows is indirect: does not scan cards, process orders, or receive deliveries. Success is measured by system adoption rates, support ticket reduction, configuration accuracy, data completeness, onboarding time-to-productivity, and uninterrupted service.
• Career Path: Started in operations management, transitioned to an IT/systems administrator role as the company digitized its supply chain. May have 5-12 years of experience in operations and SaaS platform management. Understands the Kanban-vs-ERP tradeoff: Arda is physical-first Kanban for the 80% of supplies that are easy to manage, not a full ERP.

Goals and Motivations

• Professional Goals:
  • Keep the Arda account configured correctly so the operational personas (Inventory Manager, Purchasing Manager, Receiving Clerk) can do their jobs without friction.
  • Workers can sign in without issues. Company information is accurate on purchase orders. New hires get access within their first day. The subscription tier supports the number of items and users needed.
  • Minimize support requests by configuring the system intuitively from the start.
  • Get new users productive fast. Guide each persona through their first session: first sign-in, the onboarding panel, their first scan or order. Reduce time-to-value so the team sees results before skepticism sets in.
  • Keep reference data clean and complete. Every item has a supplier, a reorder quantity, and a valid ordering link before it reaches David’s queue. Incomplete data creates friction downstream; Alan prevents it upstream.
• Motivations:
  • Set it up correctly once and not have to think about it. Reactive account management (a user cannot sign in, the billing card expired) is the worst outcome.
  • Maintaining compliance with healthcare industry regulations (accurate company records, audit trails).
  • Being the trusted go-to person for system configuration, onboarding, and troubleshooting.
  • Seeing measurable results: fewer emergency orders, less waste, less downtime, reduced stress for the team.
  • A clean item catalog where David never encounters a disabled “Start order” button because the supplier URL is missing.

Challenges and Pain Points

• Obstacles:
  • Onboarding new team members requires setting up accounts, assigning roles, and providing initial training on the card-based workflow. Must guide new users through signup, first sign-in, and the onboarding guide. Each persona needs a different introduction: Sam needs to know how to scan; David needs to understand the queue; Keisha needs to know the receiving flow.
  • Onboarding new inventory areas is the larger challenge. When Owen decides to bring hardware or adhesives under kanban management, Alan must import or create items, set up supplier references, configure reorder quantities, and prepare the first batch of cards — all before the team starts using the new area. The quality of this initial data determines whether the team trusts the system.
  • Deferred validation workflow: Initial data imports (from Amazon order history, Uline exports, or manual entry) produce items with incomplete or guessed values. Alan must accept these imperfect records, mark them for later review, and systematically validate them without blocking the team from starting to use the system. A “review later” queue or confidence indicators would help.
  • Pre-print review: Before printing the first batch of kanban cards for a new area, Alan must review critical fields (item name, reorder quantity, supplier, SKU) in a table view. Printing a card with wrong data erodes team trust and wastes laminating supplies. Alan needs a customizable review view with validation warnings (missing supplier, zero quantity, no image).
  • Vendor data completeness: Items imported from order history may have a vendor name but no supplier URL, no order method, or no SKU. Alan must fill in these gaps — ideally during a focused data cleanup session rather than having David discover them one by one in the order queue.
  • Filtering and tracking during rollout: When working through a batch of imported items, Alan needs to filter by vendor (the most reliable grouping in imported data), hide items already printed/configured, and track which items are ready vs. still need attention.
  • Company information changes (address updates, tax ID changes, NAICS code changes) must be propagated accurately across the platform for compliance and PO generation.
  • Managing multiple settings pages (Settings hub with Account/Companies/Appearance/Notifications/Display tabs, Company Settings with Company Info/Users/Subscription/Billing tabs, Account Profile) with related but distinct functionality.
  • No dedicated admin dashboard for monitoring system health and user activity. Must check the main dashboard KPIs (Total Orders, Orders Placed, Growth Rate) as a proxy.
  • Infrequent use of admin screens means they must re-orient each time they return.
• Fears/Objections:
  • Accidentally changing a setting that affects all users.
  • Billing surprises from subscription tier changes.
  • Security concerns about user access and password policies (AWS Cognito-based auth).
  • A user cannot sign in and calls them in the middle of a busy day, or the service is interrupted due to an expired payment method.
  • Printing a batch of cards with bad data and having to redo them — destroying team confidence in the system.
  • The initial data import being so messy that cleanup takes longer than manual entry would have.

Behavioral & User Environment

• Typical Day/Workflow:
  1. Weekly: Review company settings, check for pending user invitations or access requests. Review card activity and scanning compliance if wearing the Arda Manager hat.
  2. Monthly: Review subscription status, check billing, update company information if needed.
  3. Ad hoc: Onboard new team members (navigate to Company Settings > Users, invite with role, guide through signup and the “Get Started with Arda” onboarding panel). Troubleshoot user issues. Adjust notification preferences. Set up the Quickstart Kit hardware (HP 9135E dual-tray printer, laminator, scanner) for the team.
  4. During rollout phases: Import items from vendor order history. Review and clean up imported data: fill in missing suppliers, correct reorder quantities, assign item types and locations. Filter by vendor to work through items systematically. Review critical fields in a table view before printing the first batch of cards. Track which items are printed, which still need review, and which are ready to go live.
  5. Occasionally: Check dashboard KPIs (Total Orders, Orders Placed, Growth Rate) to understand platform usage and order volumes. Review stockout trends and compliance rates during monthly reviews.
  6. Strategically: Coordinate with Owen on which inventory areas to bring under management next. Plan the data preparation and user training needed for each expansion phase.
• Session Characteristics: Infrequent, purposeful sessions for account administration. During rollout and onboarding phases, sessions become longer and more frequent — potentially daily 30-60 minute data cleanup sessions when importing a new inventory area. Not a daily user in the Admin role outside of rollout phases, though they may use Arda daily in a secondary role (e.g., as Inventory Manager / Arda Manager).
• Technology Use: Office desktop or laptop, dedicated workstation (not shared). Full browser access (Chrome, 1920x1080). High technical proficiency relative to other Arda users. Comfortable with SaaS administration consoles, multi-tab workflows, and settings interfaces. Uses multiple tabs and frequently switches between Arda and email/communication tools. During data cleanup, may have a spreadsheet open alongside Arda for cross-referencing vendor order history. No scanning or printing requirements in the Admin role (these are handled when wearing the Inventory Manager hat).
• Information Sources: Arda help center articles (Quick Onboarding Guide, How to Run a World-Class Shop, Cultural Buy-In for Kanban, 10-Step Order Card Startup Guide), SaaS vendor documentation, industry compliance guides, IT admin communities. Vendor order history exports (CSV/PDF from Amazon Business, Uline, Grainger) as source data for item imports.
• Decision-Making Process: Makes system configuration decisions independently. Consults with Owen for subscription and billing changes and for strategic rollout timing. Coordinates with the Inventory Manager on workflow-affecting settings and data quality standards. May delegate day-to-day operational decisions entirely.

Personality & Work Style

• Personality Traits: Organized, cautious about changes, thorough in documentation. Prefers clear confirmation before applying system-wide settings. Wants structured pages with clear descriptions of what each option controls. Patient with data cleanup — understands that good data now prevents problems later. Takes pride in a clean, complete item catalog.
• Communication Preferences: Email for formal changes and audit trails. In-app notifications for system alerts. Prefers structured settings pages over conversational interfaces. Coordinates with operational staff (especially the Inventory Manager) about any configuration changes that affect workflows. Creates onboarding checklists for new team members and new inventory areas.

Relationship to Other Personas

• Owen (Business Principal): Owen decides what to bring under management and when; Alan figures out how and executes the data preparation, configuration, and user onboarding. Owen sets the vision (“zero stockouts by Q3”); Alan delivers the platform readiness (“all hardware items imported, validated, and cards printed by Friday”).
• Irene (Inventory Manager): Closest operational partner. Alan prepares the item catalog and card configurations; Irene takes over daily maintenance. During rollout, they collaborate closely on data validation — Irene has the domain knowledge to spot wrong reorder quantities; Alan has the platform knowledge to fix them efficiently.
• David (Purchasing Manager): Alan’s data quality directly affects David’s workflow. Every missing supplier URL or wrong order method creates friction in David’s morning queue processing. Alan aims to prevent these issues during the onboarding and data cleanup phase.
• Keisha (Receiving Clerk): Indirect relationship. Alan ensures the receiving workflow is configured correctly and that Keisha’s account and permissions are set up for her first day.