Bikesh Bhaila
1. Role Name & Department
Role: UI/UX Designer – Cashkr
Department: Design / Product
2. Reports To
Primary: IT Manager – Shahid Shaikh
Functional / Dotted-line:
CEO – Ibrahim Surya (for overall experience & brand feel)
Marketing Head – Pranjal Haldankar (for conversion-focused UX on web/app)
Works closely with: Ayaz (website), Resham (admin), Nirajan (QA), Ashwini (data), Rabina & Yaskar (SEO/content).
3. Role Purpose (1–2 lines)
Design clear, trustworthy, and high-converting user experiences across the Cashkr website, apps, vendor tools, and admin panel — turning business goals and user needs into intuitive screens and flows.
4. Key Result Areas (KRAs)
KRA 1: Consistent & Modern Design System
Create and maintain a unified design system (components, colours, typography, spacing) used across all Cashkr products.
KRA 2: UX for Core Journeys (CRO Focus)
Improve UX for critical journeys:
Sell flow: Landing → Search → Evaluation → Checkout → Order
Vendor & Admin flows where operations run daily.
KRA 3: Problem-Solving via UX
Convert user pain points (confusion, drop-offs, complaints) into better flows, copy suggestions, and layouts.
KRA 4: Clean Design Handoffs to Dev
Provide developers (Ayaz, Resham) with clear Figma files, specs, and states so implementation is fast and accurate.
KRA 5: Collaboration with Data & Marketing
Use insights from Ashwini’s dashboards, CX feedback, and marketing funnels to prioritise UX improvements that impact conversions and trust.
5. KPIs (5–8 measurable numbers)
Design Task Delivery Timeliness
% of design tasks delivered on or before agreed deadline (per sprint/month).
Design Rework Rate (Due to Designer-side Issues)
Number of times devs ask for major redesign/clarification because the design was unclear or inconsistent (aim to keep low).
Adoption of Design System
% of new features/pages using standardized components from the design system (vs custom one-off UI).
UX Issue Volume (UI/UX Complaints)
Number of UX-related complaints raised by CX/Ops/users on major flows (should reduce over time as UX improves).
Experiments / UX Improvements Shipped per Month
Count of UX changes/experiments designed and implemented (e.g., new layout, trust section, FAQ pattern, CTA changes).
Handoff Quality (Dev Feedback Score)
Simple internal rating from devs monthly (1–5) on clarity of design handoffs.
Documentation & Update Frequency (Design System)
How often design system/components are updated and documented when new patterns are introduced.
6. Core Processes Owned – SOPs
Bikesh is owner / co-owner of these UX/design SOPs:
Design System & UI Components SOP
Rules for colours, typography, spacing, buttons, inputs, cards, states, icons, empty states, error states.
How new components are added and old ones updated.
UX Flow Design SOP
How user journeys are mapped (e.g., lead → order, vendor onboarding, admin workflows) before designing screens.
Using simple user flows/wireframes before high-fidelity UI.
Design Handoff SOP
How Figma files are structured (pages, components, naming).
What devs receive: specs, spacing, responsive behaviour, states (normal/hover/disabled/error), assets.
How comments/clarifications are handled.
Feedback & Iteration SOP
How feedback from CX, Ops, Marketing, CEO, and users is collected, prioritised, and converted into UX tasks.
Cross-Platform Consistency SOP
Ensuring web, app, vendor, and admin all feel like the same brand and follow consistent patterns (navigation, buttons, error messages, etc.).
Data-Informed UX SOP
How Bikesh works with Ashwini to use funnel data, heatmaps (later), and drop-off reports to decide what UX to improve first.
7. Weekly / Monthly Reporting
Weekly Reporting
To:
IT Manager – Shahid
With visibility to: Ibrahim, Pranjal, Ayaz, Resham, Nirajan, Ashwini (as needed)
Format: Short update in Slack / Notion
Include:
Designs completed this week
Screens/flows for web, app, vendor, admin.
UX problems addressed
E.g., “Clarified final price screen”, “Improved evaluation flow layout”.
Pending clarifications
Decisions needed from Shahid / CEO / Marketing.
Next week focus
Top UX areas to work on (e.g., homepage hero, FAQ pattern, vendor dashboard).
Monthly Reporting
To:
Shahid
Ibrahim (CEO)
Marketing Head (Pranjal)
Other leads as needed
Format: 1–2 slides / short section in monthly review
Include:
Major UX improvements shipped this month
Before/after explanation for key flows if possible.
Design system updates
New components, patterns, guidelines added.
Feedback summary
Common UX issues raised and how they were solved or planned.
Next month’s UX priorities
Which flows/parts of product will be redesigned/optimized.