← All work
Case StudyTier BPrototype~2023
Divar Property Visit Scheduling Hackathon Prototype
Hackathon concept for coordinating property-visit scheduling around a classifieds journey.
ProductTechnical
Context
~2023 · Hackathon prototype · Maturity: Prototype.
Problem
Scheduling visits around property listings creates coordination friction between interested users and listing owners/agents.
Users
Hackathon/product-design context.
My Role
4-person team; product idea/design and technical discussion.
Product Decisions & Responsibilities
- Contributed to problem framing, product idea, and interaction design.
Technical Approach
- Participated in technical feasibility discussion.
Product designTechnical feasibility
Constraints
- Number of competing teams is not documented.
- Prototype/hackathon context only.
Product Flow
- Open listing
- Request visit slot
- Coordinate availability
- Confirm appointment
Outcome
- Roughly 5th place in the hackathon.
What I Learned
- Distribution and workflow context can matter as much as feature novelty.
Evidence Boundary
What this does — and does not — prove
Rank remains approximate; competitor count is not claimed.
Next Iteration
Extend the product only after the next decision can be tied to stronger user, operational, or business evidence rather than adding features for their own sake.