Teno — rescuing an MVP under fire
A property management platform for landlord-tenant communication, task tracking, and finance management.
What I Did
-
Took ownership of product definition during a phase with unclear requirements and no strong product direction, helping the team move from scattered ideas to a structured and realistic MVP plan.
-
Led discovery sessions to clarify terminology, user roles, and permissions. Using OOUX-style object mapping, I simplified the system model and created a shared glossary, which aligned the client, designers, and developers around the same product logic.
-
Structured the MVP scope by defining core flows, objects, and priorities, turning an expanding feature list into a roadmap the team could actually deliver.
-
Built a live Design System in code with Cursor so the junior frontend team could reuse components, reducing implementation errors and speeding up development.
Challenges & Iterations
-
Unclear roles and product logic. Stakeholders and developers used different terms for the same concepts, which slowed down both design and development. I introduced a shared glossary and simplified roles and permissions, making the product easier to understand, build, and maintain.
-
Design–development gap. Limited frontend experience caused inconsistencies between Figma and the final UI. I created a coded component library with Cursor that mirrored the design system, allowing the team to implement screens faster and with fewer corrections.
-
Team changes during development. With turnover mid-project, new developers needed context quickly to continue the work. I documented flows, components, and usage rules, and ran walkthroughs so new team members could onboard faster without breaking existing logic.
