A game is a value-contract system.
We examine how player time, money, effort, passion, and trust return as meaningful value.
HOW NOVASMC THINKS · PUBLIC METHODOLOGY
A game is not a collection of features. It is a system through which value is delivered.
NOVASMC begins with direct play, connects structure, perception, behavior, and economy, and turns the result into an executable decision.
01COREOne core philosophy
04METHODSFour decision questions
02LENSESTwo expert review lenses
03ENGINESThree execution engines
CORE PHILOSOPHY
We do not stop at describing the result.
We examine the full path through which value is built, perceived, and translated into behavior and business value.
Connect causes before reacting to signals.
Data shows what happened; direct play and structural analysis help explain why.
Review the rules before adding volume.
We look for change in rules, flows, and relationships before relying on more production cost.
FOUR METHODOLOGIES · FOUR QUESTIONS
The question comes before the name of the method.
The four methods are not a fixed package. We combine the perspectives required by the client's decision question.
01
STRUCTURAL DIAGNOSISSFA
What is missing or structurally misaligned?
We read progression, competition, cooperation, content structure, growth systems, economy, gacha, shops, and events as one connected game structure.
- PUBLIC SCOPE
- 10-system structure
- DECISION OUTPUT
- Structural risks and priority review points
02
VALUE-GAP ANALYSISMDML
Is the value built the same as the value players feel?
We compare value provided through design, systems, and operations with value perceived through experience, needs, and engagement.
- PUBLIC SCOPE
- Provider 27 + Customer 27
- DECISION OUTPUT
- Value-delivery gaps and priorities
03
CAUSAL BUSINESS LINKM-ABC
How does structure shape behavior and business value?
We connect game architecture, player behavior, and sustainable business value in one causal chain to locate where the flow breaks.
- PUBLIC SCOPE
- Architecture → Behavior → Commerce
- DECISION OUTPUT
- Map of behavioral and business effects
04
CONTRADICTION RESOLUTIONNTRIZ
Can the conflict be solved without continually adding cost and content?
Instead of ending with compromise, we redesign rules, time, space, form, and operating relationships around conflicting goals.
- PUBLIC SCOPE
- Four innovation axes
- DECISION OUTPUT
- Executable solutions within constraints
FROM EVIDENCE TO DECISION
Each methodology meets in one decision path.
We separate structure, value gaps, behavioral and business effects, and contradictions before connecting them into one direction.
- 01 · EVIDENCEDirect play and game knowledge
- 02 · DIAGNOSESFA + MDML
- 03 · CONNECTM-ABC
- 04 · RESOLVENTRIZ
- 05 · DECIDECustom execution
Methodology explains how judgment is formed. The six engagement steps are explained separately in How We Work. View How We Work
TWO EXPERT LENSES
Economic and perceived value belong in the same decision.
We show how Ph.D.-level disciplines deepen the methodology without publishing personal profiles.
Financial Engineering Ph.D. Lens
We review currency creation, spending, accumulation, prices, rewards, probabilities, player-cohort gaps, and adjustment levers as a living economy.
CONNECTED METHODSSFA economy · M-ABC business value · E² economy and offer records
Color Design Ph.D. Lens
We review how hue, value, saturation, and palette choices shape attention, readability, emotion, brand perception, and preference.
CONNECTED METHODSSFA graphics · MDML design-experience gap · MPM perception review
EXECUTION EVIDENCE
The concepts continue into real inputs, checks, and outputs.
The public site explains roles and outputs while protecting detailed formulas, questionnaires, and client data.
Connect progress, bottlenecks, economy, offers, and qualitative evidence along the direct-play timeline.
Scenes and changes that can be checked again
Organize and cross-check the S1–S10 game structure with sources, evidence types, and confidence.
A comparable structural map
Compare Provider and Customer perspectives across multiple player types to identify value gaps.
Prioritized value gaps
PUBLIC / PROTECTED BOUNDARY
Show the expertise. Protect clients and internal engines.
- PUBLIC
- Philosophy, questions, scope, and output roles
- PROTECTED
- Personal data, client data, formulas, internal codes, and guaranteed results
START WITH THE DECISION
Share the question that needs to become clear.
After reviewing the situation and available evidence, we propose the methods, expert lenses, and smallest useful scope.