01 // start with the Problem
Purpose
Not every production problem needs another custom system.
Sometimes an existing framework already covers the requirement. Sometimes a lightweight integration is enough. In other cases, custom development is the cleaner long-term choice.
The goal is to determine that before unnecessary implementation work begins.
02 // Project Assessment
What we review
Understand the requirement in its real project context.
We Look At
A technically valid solution can still be the wrong choice if it ignores the systems and workflows around it.
- The problem you are trying to solve
- Current project structure
- Relevant existing systems
- Unity version
- Package requirements
- Required integrations
- Workflow requirements
- Team requirements
- Technical constraints
- Future extension needs
- Maintenance requirements
03 // Recommendations
Outcomes
The right answer is not always one of our products.
The purpose of the review is to determine the sensible implementation path, not to force a Red Corp. product into every project.
Existing Framework
A Red Corp. framework fits the requirement without significant modification.
Framework + Implementation
A framework fits but needs project-specific configuration or integration.
Framework + Extension
The existing foundation is suitable but requires additional project-specific functionality.
Third-Party Solution
Another existing product is better suited to the requirement.
Custom Development
The problem is sufficiently project-specific that a custom implementation makes more sense.
No Change
The existing system may already be adequate and not justify replacement.
04 // Finding the right Approach
Not sure which system you need?
Describe the project, the problem, and what you need the workflow or system to accomplish.