🧠 Experimental Project（Personal Exploration）

Real process. Reusable thinking.

This is a self-initiated UX case study exploring how teams can better share company-specific knowledge that typically isn't documented or easily searchable, supporting distributed and cross-functional collaboration.

Tipshelf is a concept for an internal tool designed to help teams work more effectively by sharing and reusing company-specific knowledge—like internal frameworks, tools, and undocumented solutions—that isn't easily searchable online.

By making critical knowledge accessible, it helps reduce duplicated effort, speed up problem-solving, and improve overall team efficiency.

<aside> ✏️

This project is a UX case study derived from the ideas and insights explored in my earlier reflection, “Cultivating a Knowledge Sharing Habit in Global Teams.” While that piece focused on the challenges of sharing undocumented, company-specific knowledge in distributed teams, this case study turns those insights into a practical concept for an internal knowledge-sharing tool.

</aside>

🔸 1. User Personas

👤 Lisa – Junior UX Designer / Knowledge Seeker

• Role: Junior UX Designer (1st year)
• Context: Remote team, recently joined a cross-functional product squad
• Pain Points:
  • Often unsure how to solve unfamiliar problems
  • Finds it hard to locate useful insights beyond project-specific docs
• Goals:
  • Learn from others’ experiences, not just decisions
  • Gain confidence through understanding past processes and problem-solving steps
• Usage Scenarios:
  • Lisa struggles with designing a user flow with branching logic. Searching through Slack gives her decisions, but not the reasoning.
  • Using Tipshelf, she finds a post by a peer sharing how they explored multiple options and used team feedback to narrow down the flow.
  • Because the post is tagged with Figma, Flow Design, and Prototype, Lisa finds it easily and is able to explore related tips as well.

👤 Anna – Mid-level Engineer / Knowledge Contributor

• Role: Mid-level Engineer (3rd year)
• Context: Contributing to shared practices and mentoring new members
• Pain Points:
  • Initially found knowledge sharing vague and effortful
  • Unsure if her shared tips were useful or acknowledged