Haz que se destaque.
Todo empieza con una idea. Tal vez quieras comenzar un negocio o convertir un pasatiempo en algo más. O bien, es posible que tengas un proyecto creativo para compartir con el mundo. Sea lo que sea, la manera en la que cuentes tu historia online puede marcar la diferencia.
The Harada Method breaks down ambitious goals into 64 actionable cells across 8 key domains, ensuring nothing is overlooked and every dependency is mapped. This adapted version is designed for AI-native projects, incorporating considerations for autonomous agent capabilities, prompt engineering quality, model selection rationale, and continuous learning loops. Use this framework to document your project comprehensively for portfolio presentation, stakeholder review, or team handoff.
Preguntas frecuentes
How to use it
Open with a single sentence that captures what your system does and the core value it provides to users.
Walk through a quick start guide with three to five numbered steps that take a new user from zero to a working result. Each step should be a concrete action that someone unfamiliar with your project can follow.
Describe the primary interface through which users interact with your system, whether that is a command-line tool, a web application, an API endpoint, an autonomous agent, or a notebook environment.
Explain the input-output contract clearly. Describe exactly what the user provides as input, including file types, data formats, or natural language queries. Then describe what your system produces as output, including deliverables, artifacts, or transformed data.
Goal
State your north star objective as a single ambitious and measurable goal that this project achieves. This is the center cell of the Harada Matrix from which all other cells derive their purpose.
Present your success metrics in a table format with four columns: the metric name, the baseline measurement before the project, the target measurement that indicates success, and the current measurement showing progress. Include three to five metrics that would convince a skeptical stakeholder that the project succeeded.
Specify the timeframe for achieving this goal, whether it was a single sprint, a quarter, or a long-term initiative spanning multiple quarters.
Why
Articulate the problem statement as a clear description of the pain point, inefficiency, or gap that this project addresses. Explain who experiences this problem and how frequently.
Identify your target users by describing the primary audience who benefits most directly from this solution, as well as secondary audiences who receive adjacent benefits.
Construct a value proposition by contrasting the world without your solution against the world with it. Describe the previous state, including workarounds people used and the costs they incurred. Then describe the transformed state after your solution is in place.
Create a differentiation comparison showing existing solutions against your approach. For each limitation of current tools or methods, explain the corresponding advantage that your project provides.
8 domains
Break your central goal into eight supporting objectives, each representing a domain that had to succeed for the overall goal to be achieved.
The first domain is Core Functionality, which addresses what had to work for the system to deliver any value at all.
The second domain is Data and Knowledge, which covers what information, training data, or knowledge bases the system required. The third domain is User Experience, which defines how users interact with the system and what makes that interaction intuitive. The fourth domain is the AI and Agent Layer, which specifies what autonomous capabilities the system possesses and how it reasons or decides. The fifth domain is Infrastructure, which determines where the system runs and what computational resources it requires. The sixth domain is Quality and Testing, which establishes how correctness is verified and what testing strategies were employed. The seventh domain is Integration, which identifies what external systems, APIs, or services the project connects to. The eighth domain is Growth and Learning, which explains how the system improves over time through feedback, retraining, or iteration.
For each domain, provide the supporting goal you set and indicate whether that domain is complete, in progress, or blocked.
¿Esta es una pregunta frecuente?
Todo empieza con una idea. Tal vez quieras comenzar un negocio o convertir un pasatiempo en algo más. O bien, es posible que tengas un proyecto creativo para compartir con el mundo. Sea lo que sea, la manera en la que cuentes tu historia online puede marcar la diferencia.
¿Esta es una pregunta frecuente?
Todo empieza con una idea. Tal vez quieras comenzar un negocio o convertir un pasatiempo en algo más. O bien, es posible que tengas un proyecto creativo para compartir con el mundo. Sea lo que sea, la manera en la que cuentes tu historia online puede marcar la diferencia.
Preguntas frecuentes
What worked
Document your key wins by listing three to five technical or design decisions that paid off. Each win should describe the decision you made and the positive outcome it produced.
Extract reusable patterns by identifying code snippets, prompt templates, or architecture patterns that proved effective and could be applied to future projects. Include the actual code or template text when possible.
Note any unexpected successes where something worked better than you anticipated. Explain what your original expectation was and what actually happened.
Challenges
Document significant challenges you encountered during the project. For each blocker, describe the challenge itself, the root cause that created it, and the resolution that ultimately solved it or the current mitigation if it remains unresolved.
List technical debt you incurred during the project. For each item, describe the shortcut you took, why it was necessary at the time, and what risks or costs it creates for the future. Reflect on lessons learned by answering three questions. First, what would you change if starting this project over from scratch. Second, what decisions would you keep exactly as they were because they proved correct. Third, what alternative approaches would you explore that you did not consider originally.
Requirements
Enumerate the hard requirements that your system had to satisfy to be considered functional. These were the non-negotiable capabilities without which the project would have failed to deliver its core value. Include both functional requirements describing what the system does and non-functional requirements describing performance, security, reliability, or compliance constraints.
List the soft requirements that enhanced the system but were not essential for initial viability. These were features or qualities you deferred to future iterations.
State the constraints that bounded the project. Describe the budget ceiling including both monetary costs and computational costs such as API tokens. Specify the timeline including hard deadlines and any external dependencies on dates. Identify dependencies on external services, APIs, models, or team members that blocked or could have blocked progress.
Tools
Todo empieza con una idea. Tal vez quieras comenzar un negocio o convertir un pasatiempo en algo más. O bien, es posible que tengas un proyecto creativo para compartir con el mundo. Sea lo que sea, la manera en la que cuentes tu historia online puede marcar la diferencia.