Chapter 16: Multi-Stage Rendering Workflow

10-15% Rule Application: Multi-stage rendering increases keeper rate by allowing style testing and refinement at each stage

Content:

Understanding Multi-Platform Rendering Strategy

• Why single-platform rendering isn't enough
• Benefits of staged rendering approach
• Cost-benefit analysis of multi-stage workflow
• Time management across platforms
• When to use simplified vs. full multi-stage pipeline

Stage 1: MidJourney Concept Development

• Using MidJourney for Initial Concepts:
• Why MidJourney excels at concept exploration
• Rapid iteration and style discovery
• Translating storyboards to MidJourney prompts
• Generating multiple concept variations
• Selecting winning concepts for next stage
• MidJourney's strengths and limitations

• MidJourney Workflow Best Practices:
• Prompt engineering for concept phase
• Using MidJourney parameters effectively
• Aspect ratio and composition planning
• Style reference techniques
• Image weight and remix strategies
• Upscaling decisions for next stage

Stage 2: Nano Banana Realistic Rendering

• Why Nano Banana After MidJourney:
• Nano Banana's realistic rendering capabilities
• Taking concepts to photorealistic execution
• Using MidJourney concepts as Nano Banana references

• Multiple Style Passes in Nano Banana:
• Game Style Rendering:
• Characteristics of game-style aesthetics
• Prompt engineering for game style
• When to choose game style for projects

• Movie Style Rendering:
• Cinematic quality characteristics
• Prompt engineering for movie/film style
• When to choose movie style for projects

• Style Comparison Strategy:
• Running parallel style passes
• Presenting both options to clients
• Combining elements from different styles
• Managing render time and credits across styles

• Nano Banana Workflow:
• Importing MidJourney concepts
• Reference image utilization
• Prompt translation from MidJourney to Nano Banana
• Quality settings and parameters
• Batch rendering strategy
• Selection criteria for Stage 3

Stage 3: Figma Corrections & Refinement

• Bringing Renders into Figma:
• Import organization and layer structure
• Setting up correction workflows
• Comparison frames (concept vs. render)

• Correction Types by Stage:
• Minor fixes (continue to finalize)
• Major issues (flag for re-render)
• Enhancement opportunities

• Figma Tools for Stage 3:
• Vector corrections on rendered outputs
• Color grading and adjustment
• Compositing multiple renders
• Adding final polish details
• Preparing presentation layouts

Stage 4: Decision Point - Re-render or Finalize

• Decision Framework:
• Quality threshold assessment
• Re-render vs. correction cost-benefit
• Client feedback integration
• Timeline considerations

• When to Re-render:
• Critical errors that can't be fixed in Figma
• Style direction changes
• Better concepts discovered in process
• Client revision requests
• Using corrected version as new reference

• When to Finalize:
• Quality meets or exceeds standards
• Corrections are sufficient
• Timeline or budget constraints
• Diminishing returns on further iteration

Managing Assets Across Platforms

• File Naming Conventions:
• Consistent naming across MidJourney, Nano Banana, Figma
• Version control systems
• Stage identifiers in filenames
• Project organization structure

• Asset Tracking:
• Spreadsheet/database for multi-stage tracking
• Status tracking: Concept/Render/Corrected/Final
• Platform settings documentation
• Prompt library maintenance

• Cross-Platform Consistency:
• Maintaining style across platforms
• Color management considerations
• Resolution planning for each stage
• Metadata and reference preservation

When to Use Which Tool for Which Stage

• Platform Decision Matrix:
• MidJourney strengths: Concept, style exploration, artistic
• Nano Banana strengths: Realism, specific styles, refinement
• Figma strengths: Corrections, compositing, presentation

• Alternative Workflows:
• Simplified 2-stage: MidJourney → Figma
• Simplified 2-stage: Nano Banana → Figma
• Direct to final: When to skip stages
• Adding additional platforms (when and why)

Practical Elements:

• Complete Multi-Stage Workflow Diagram
• Exercise 1: Take one storyboard panel through all 4 stages
• Exercise 2: Compare game vs. movie style renders in Nano Banana
• Exercise 3: Create asset tracking system for multi-platform project
• MidJourney to Nano Banana prompt translation guide
• Platform decision flowchart
• Asset naming convention template
• Multi-stage project tracker (spreadsheet/Figma template)
• Side-by-side comparisons: Stage 1 → Stage 2 → Stage 3 → Final

• Cost breakdown: Multi-stage vs. single-platform
• Time analysis: Efficiency gains from staged approach
• ⚡ Quick Win: Simplified 3-stage workflow for tight deadlines