Work, Made Playable

The description states that Work, Made Playable is a game-native career portfolio built around real professional experience. It features:

• A pixel-art studio containing interactive objects connected to parts of the author’s work (e.g., game design, technical art, UI/visual design).
• A character loadout interface, where different professional roles are represented through animated scenes.
• A Mission Board for browsing projects by discipline.
• The system uses structured data to render multiple disciplines and project types.
• It is built as a static website using HTML5, CSS3, JavaScript, Python, Pillow, and AI tools like Codex and GPT-5.6.

The author notes that this is an early prototype, not yet a universal tool or platform.

“The current project is intentionally built around my own career. It is the first working example, not yet a universal portfolio generator.”

The author positions Work, Made Playable as a way to translate real professional experience into play without losing honesty or clarity. The core idea is to make a person’s identity easier to understand at a glance through visual storytelling.

Key claims include:

• The project aims to help people express their work in ways that conventional CVs cannot.
• It allows users to represent skills and projects through relevant props, environments, and short animations.
• It is intended to be a personalised, interactive introduction website, not a replacement for the CV.

There is no indication of prior positioning or evolution beyond this single self-reported version. The author does not describe any market research, user feedback loops, or product iterations beyond their own use case.

“Instead of asking visitors to begin with a conventional CV, I wanted them to enter a space, discover objects, select different professional roles and gradually understand what kind of designer I am.”

The description does not clearly define target customers or an ideal customer profile (ICP). However, the author implies that the system could be useful for:

• Multidisciplinary creators
• Career changers
• People whose work is hard to explain via a traditional CV

It is unclear whether the author has identified specific personas or tested with real users beyond themselves.

“The larger idea could become a reusable system for multidisciplinary creators, career changers and other people whose work is difficult to explain through a conventional CV alone.”

There is no evidence of a business model or pricing structure in the description. The author describes the project as a personal prototype, not yet a commercial offering.

“The current project is intentionally built around my own career. It is the first working example, not yet a universal portfolio generator.”

No mention of monetization, subscriptions, licensing, or any revenue-generating mechanism.

The author reports building the prototype using:

• HTML5
• CSS3
• Vanilla JavaScript
• Python and Pillow for animation processing
• OpenAI Codex and GPT-5.6
• GitHub Pages

It is a static website, with no runtime framework or package dependencies.

The system uses a layered asset system for interactive objects, and includes:

• Day/night presentations
• Animated hover states
• Responsive design alternatives
• Structured data storage to support multiple disciplines

“Project and case-study content is stored as structured data so the same components can render multiple disciplines and project types.”

There is no evidence of traction, customers, or adoption beyond the author’s own use. The project is described as:

• A personal prototype
• Not yet a universal portfolio generator
• Built for self-use only

No metrics, user feedback, or usage data are provided.

“The current project is intentionally built around my own career. It is the first working example, not yet a universal portfolio generator.”

There is no evidence of competitive analysis or awareness of existing tools in this space. The author does not reference competitors or similar platforms.

“No mention of existing tools or platforms that do something similar.”

• Lack of external validation: No customers, users, or third-party feedback.
• Unproven commercial viability: The system is described as a prototype, not a product.
• Limited scalability assumptions: No indication of how it would scale beyond one individual’s use case.
• Self-reported nature: All claims are unverified and based on the author's own account.

“Everything above is the authors' own account. It is not independently verified.”

1. What specific problem are you solving, and how does this solution differ from existing portfolio tools?
2. Have you tested the prototype with real users beyond yourself?
3. Are there any early adopters or potential customers who have expressed interest in using this system?
4. How do you plan to transition from a personal prototype to a scalable product?
5. What is your roadmap for monetization, if any?