IKAM
IKAM provides a centralized and transparent system for managing replacement vehicle allocation processes by offering a customized platform for authorized dealers, headquarters, and admin users.
Overview of the IKAM System
IKAM ensures that replacement vehicle allocation processes are managed quickly, efficiently, and seamlessly. Beyond request creation, it offers users a more effective experience with features such as file tracking, reporting, and notification systems.
Dashboard
I designed a role-based dashboard for IKAM that makes replacement-vehicle processes measurable and traceable by consolidating case flow, notification volume, and the real-time work queue into a single view.”
User Login and Registration Processes
Users log in with their email and password.
If the password is forgotten, it can be reset via email.
Kullanıcı hesapları admin tarafından oluşturulur ve yetkileri atanır.
Replacement Vehicle Allocation Process
File Creation: Requests initiated by authorized dealers are referred to as “files.” In IKAM, creating a new file involves four key steps:
-
Survey: The user is presented with a series of yes/no questions to determine the vehicle’s eligibility for replacement.
-
If the result is positive: The request proceeds to the next step.
-
If the result is negative: The user is given the option to exit the survey or choose “Proceed Anyway.”
Replacement Vehicle Allocation Process
Customer Information: Details such as name, phone number, and email are entered
Replacement Vehicle Allocation Process
Vehicle Information:
The chassis number is entered, after which the mileage, license plate, and model details are automatically retrieved.
Replacement Vehicle Allocation Process
Vehicle Information:
The chassis number is entered, after which the mileage, license plate, and model details are automatically retrieved.
Replacement Vehicle Allocation Process
Customer Information: Details such as name, phone number, and email are entered
Replacement Vehicle Allocation Process
Vehicle Information:
The chassis number is entered, after which the mileage, license plate, and model details are automatically retrieved.
Replacement Vehicle Allocation Process
File Completion
-
Request Type: Spare Part Waiting, Fault Diagnosis, Repair, etc.
-
Description: Details of the request are entered.
-
Attachments: Required documents are uploaded.
-
Final Step: The file is submitted to the headquarters pool.
User Interfaces
Authorized Dealer
Enters customer requests into the system, creates files, and communicates with the headquarters.
Headquarters
Manages requests from authorized dealers, reviews files to make decisions, and generates reports.
Admin Panel
Manages all system modules, configures dashboard content, and controls user permissions.
System Advantages
-
Fast Processes: Request creation and approval steps are streamlined.
-
Transparent Tracking: All file activities are recorded and viewable.
-
Reporting: Provides performance analysis based on data.
Authorized Dealer Request Detail Page
Context
IKAM is a replacement-vehicle CRM where each “file” (case) gathers many stakeholders and modules. This page already existed and was actively used, but the information density and multi-module nature created friction during daily operations.
Problem
-
Users needed to understand the current case stage instantly; otherwise they relied on extra calls/messages.
-
Moving across modules (replacement, pricing, vehicle, etc.) risked losing context.
-
Key fields (notes, descriptions, status) were easy to miss, increasing “search & verify” time and error risk.
Solution
I shaped the page into a clear case hub that supports fast reading and safe actions:
-
Anchored the workflow with a stepper/status indicator at the top so the stage is always visible.
-
Used a tab-based structure to navigate modules while keeping the case context intact.
-
Improved the content hierarchy so high-frequency operational info (e.g., explanation/notes) is easy to scan.
-
Kept “case identity + quick controls” separate from the main working area to reduce cognitive load.
My Role
UI/UX Designer (end-to-end UX/UI improvements on an existing product area)
Responsibilities
-
Information architecture: page hierarchy, sectioning, navigation patterns
-
UI hierarchy and readability improvements for high-density content
-
Consistency across repeated patterns/components and interaction states
-
Operational UX: optimizing for speed, scanning, and error prevention
Outcomes
-
Faster “where are we in the process?” understanding at a glance
-
More controlled cross-module navigation without losing context
-
Reduced effort spent on searching/confirming details inside the file
Attachments: Centralized all case-related documents in one place to speed up validation and strengthen auditability.
Forum: Enabled case-based communication logging to improve cross-team coordination and reduce context loss.
Goodwill: Structured exceptional goodwill gestures into a controlled, traceable flow to support consistent, well-justified decisions.
Activity History: Made every critical action on the case trackable to increase operational transparency and audit confidence.
Replacement Vehicle Details: Clarified allocation, handover, and return details within the case context to accelerate coordination and decision-making.
Survey: Linked case closure to customer feedback to support a continuous improvement loop.
Case Hub: Workflow Tracking & Modules
Reference Details
In replacement-vehicle operations, “reference” is a critical matching key (insurance, case linkage, dealership/service routing). Mistakes here typically surface late and cost time.
Responsibilities
-
Designing a scalable reference pattern (works well even with multiple entries)
-
Structuring details for verification speed (grouping + readable blocks)
-
Defining interaction and edit controls for data safety
-
Ensuring UI consistency with the overall CRM system patterns
Outcomes
-
Faster reference lookup and verification with less scrolling/searching
-
Lower risk of progressing with wrong/unchecked reference data
-
Cleaner operational handoff: the right details are visible in the right place
Draft Requests — Resume / Edit Flow
This screen allows authorized dealers to review and manage requests that were started but not submitted yet. Users can reopen a draft, complete missing information, edit details, and continue the process from where they left off.
-
Lists all incomplete requests in one place, reducing rework and repeated data entry.
-
The “Continue” action opens the selected draft instantly, enabling users to complete and submit the request efficiently.
-
A search field helps users quickly locate a specific draft, improving findability in long lists.
Head Office Request List
I designed a centralized operational screen for HQ that consolidates all requests into a single queue, provides clear ownership (assigned/unassigned) and status visibility, and streamlines the assignment flow.
Conclusion
IKAM is a UX-driven operational platform designed to simplify the end-to-end replacement vehicle allocation workflow across authorized dealers, HQ teams, and admin users. By turning a multi-step, validation-heavy process into a structured, traceable experience, the system helps users find the right information faster, manage documents securely, and collaborate transparently within the context of each case.
From a product design standpoint, IKAM demonstrates effective digital transformation through a modular IA (information architecture), consistent interaction patterns, and accessibility-aware UI decisions. The result is a user-friendly interface that supports both speed and accuracy—reducing operational friction, improving service quality, and enabling measurable gains in internal efficiency and accountability