Tekion Corp · Overview
Thanks for Visiting
Reach out

100's designers in the Design Baywith the Founders
Context
Two years, in full · ~7 min read
The Brief
Two years inside the software a dealership runs its whole day on.
Tekion puts a dealership's whole operation on one cloud platform. Founded 2016, Pleasanton, 1,100+ retailers live. The problem is what that looks like from the inside.
I designed inside it for two years, across ARC and DRP, ticket by ticket. The solution is all 255+ of them, and the output is the 2 tracks worth showing in full.
The outcome is what changed, and the recommendations under it are what the people I worked with said. Best part: a design bay of a hundred designers, each with a different perspective, teaching each other daily.
Detailed case studies
- OperationsParts Receiving Revamp
- RetailThe dealership-facing side
255+
Tickets handled
Across two years on the floor
6
Brands
Honda, Ford Pro, GM, RRG, Asbury and Aurora
2
Platforms
ARC (Automotive Retail Cloud) and DRP (Digital Retail Platform)
3
Client countries
United Kingdom, Canada and United States
27+
Projects end to end
Carried from problem to ship
127+
Handoffs and QA rounds
Design handoff and QA feedback
What is Tekion
The platform, before the tickets
Who brings it in
The brands I designed for: Honda, Ford Pro, GM, RRG, Asbury and Aurora. They choose the platform and set the rules a dealership runs by.
Who uses it all day
Receiving clerk
Checks parts in against the order, damaged or short.
Salesperson and F&I
Builds the deal, the trade in, the lender and the contract.
Cashier and accounts
Takes payment at the invoice and keeps the books right.
Dealer admin
Sets up sales rules, taxes, fees, lenders and rebates.
Orders and stock
Orders vehicles, tracks where they are, and builds quotes.
Sales and follow up
Works the leads, the meetings, the notes and the tasks.
OEM teams
Run the brand's portal, dashboards and dealer enrolment.
Read from the areas the ticket titles name. 1 role is named outright: the Receiving Clerk.
How a ticket moved
The route, step by step
From the PM raising it to feedback from the floor: 15 steps in 5 phases, with 2 approvals before the handoff. Read it phase by phase; each step names the roles in it. The 127+ handoffs and QA rounds in the Context grid went through the last 2 phases.
01Frame
- 01PM raises the ticketPM
- 02First discussionThe core reason, and whyDesign · PM
- 03Direction decidedDesign
02Understand
- 04Client meetingTo understand themDesign · Client
03Design
- 05Design and buildDesign
- 06First approvalClient
- 07ReviewDesign · PM · Dev
- 08Design and buildApproved by 3 teamsDesign · PM · Dev
- 09ReviewDesign · PM
04Handoff
- 10Design handoffDesign · Dev · PM
- 11BuiltDev
05Ship
- 12QAWhole team
- 13Design QADesign
- 14DeploymentWhole team
- 15FeedbackWhole team
- Design in the room
- Approval
All the Issues Handled
Every ticket, from the Jira export
Priority, name and status are the export's own values. Design Type is derived from each ticket's title, so it is a reading rather than a field that came out of Jira.
Showing 10 of 255
| Ticket Name | Design Type | Status | |
|---|---|---|---|
| P0Highest | Adhoc - Add of Manual in Program | Feature Design | Complete |
| P0Highest | Adhoc - Address Logical Change in Analytics | Enhancement | Complete |
| P0Highest | Cashiering at Invoice Level | Feature Design | Complete |
| P0Highest | Cashiering Feedback | Feedback | Complete |
| P0Highest | Creation of RO from Deals side for Products/Accessories sold[S] - PO | Feature Design | Complete |
| P0Highest | Fleet deal enhancement | Enhancement | Complete |
| P0Highest | Imbalanced Contract in Deals | Feature Design | Complete |
| P0Highest | Cashiering at Invoice Level | Design Review | Complete |
| P0Highest | Cashiering at Invoice Level | Design Review | Complete |
| P0Highest | Cashiering Feedback | Design Review | Complete |
31 tickets. Higher impact, lower effort.
P0HighestGoes first
67 tickets. Higher impact, higher effort.
P1HighPlanned in
157 tickets. Lower impact, lower effort.
P2MediumFits around the rest
0 tickets. Lower impact, higher effort.
P3Rarely reaches design
- Parts45 of 255
- Deals and F&I45 of 255
- OEM portals and analytics44 of 255
- Setup, taxes and fees30 of 255
- Orders and vehicles24 of 255
- CRM and follow up17 of 255
- Cashiering and accounting14 of 255
- Ad-hoc and platform wide36 of 255
Read from each ticket's title, like Design Type: the export has no module field. A title naming 2 areas counts once, under the first rule it matches.
Featured Projects
The two tracks the work split into
Those two years split into two tracks. Retail is five projects from the dealership-facing side; Operations is the Parts Receiving Revamp, as it was presented.
Outcome
What the two years moved
These are the figures I carry on my CV, counted on the same work the ledger above lists. 4 are from the product design role and 2 from the internship before it.
160
Hours saved a year
Design system handoff standardised across global brands
190
Deliverables launched
Delivery cycles accelerated by 12 days
3
Minutes off each task
Cashiering workflows, and 50 hours a month per dealership
AAA
WCAG 2.2 conformance
Complex B2B platforms, 10,000 global users
6
Minutes off data entry
AI backed verification across 5 pilot environments
65
Fewer support tickets
A/B testing and heuristics across 150 daily tasks
Recommendations
What the people I worked with said
UX Designer, Oracle
I had the pleasure of working with Deepak who is a talented designer and consistently showcased a strong work ethic, a willingness to learn, and a positive attitude. His dedication to his tasks and his commitment to delivering high-quality work was truly impressive. His strong collaboration and communication skills made him an invaluable asset and that was something to learn from him. I have no doubt that Deepak will continue to excel in their future endeavors, and I highly recommend him for any opportunity that comes his way.
UX Designer, Alteryx
As Deepak's mentor at Tekion, I witnessed his dedication, hard work, curiosity to learn new things, and sincerity firsthand. Throughout his internship, Deepak consistently demonstrated remarkable dedication to his work. He always went above and beyond what was expected of him, often putting in extra hours to ensure that projects were completed to the highest standard. Deepak's commitment to excellence was evident in his attention to detail and willingness to take on challenging tasks enthusiastically.
What I'd carry forward
Reflection
01
The foundation, and the workflow
2 years built the foundation of how I design, and how to carry it through a complex workflow of reviews, approvals, handoffs and QA.
02
The business behind the design
Every screen sits on a dealership's money, rules and time. What the business needs comes before what the screen looks like.
03
The core, and the root cause
Before drawing anything, find what the problem really is and why it happens, not only what the ticket asks for.
04
Learn from the bay
A design bay of a hundred designers, each with a different perspective, teaching each other daily.







