How to Engineer Better Inputs: The Data/Context Moves That Beat Better Prompts

I spent two hours crafting the perfect prompt. The AI output was still garbage.

I tried adding instructions. I used chain-of-thought reasoning. I gave it examples. Nothing worked.

Then I changed one thing: Instead of asking AI to "analyze our operational pain points," I uploaded the actual process documentation, the capability framework we use, and three examples of previous analyses with our tone and format.

The output went from unusable to client-ready in one attempt.

That's when I realized: I'd been optimizing the wrong variable. The problem wasn't my prompt. It was my context.

Most people obsess over prompt engineering—finding the magic words that make AI perform. But recent research from Anthropic reveals a fundamental shift: "Building with language models is becoming less about finding the right words and phrases for your prompts, and more about answering the broader question of how to architect the context in which those prompts operate".

Organizations implementing structured context engineering are seeing 3x faster AI deployment, 40% reduction in operational costs, and 90-95% accuracy improvements. The difference isn't better prompts—it's better inputs.

Why Your Prompts Keep Failing

Here's the uncomfortable truth: You can't prompt your way out of a context problem.

When AI produces poor results, most people assume they need a better prompt. But the real issue is usually one of three context failures:

1. Missing Source Material

You're asking AI to "write a capability assessment" without giving it your actual capability definitions, your client's organizational structure, or examples of what "good" looks like in your work.

The result: AI generates generic consulting-speak that sounds plausible but doesn't reflect your methodology or your client's reality.

2. Ambiguous Standards

You want AI to match your writing style, but you haven't shown it examples of your previous deliverables. You expect it to follow your quality bar, but you haven't defined what that bar is.

The result: AI produces work that's technically correct but feels wrong—off-brand, too formal, too casual, or missing your signature analytical depth.

3. Incomplete Instructions

You're giving AI a creative writing task (like prompt engineering) when what you need is a structured data task. You're asking it to "figure out" things it should be told explicitly.

The result: Hallucinations, inconsistencies, and outputs that require so much editing you might as well have written it yourself.

The pattern is clear: Prompting is linguistic tuning. Context is systems thinking. You can't tune your way to reliability if the system doesn't have the right information to begin with.

The Context Engineering Framework

Context engineering means designing the information environment AI operates within. It's not about what you ask—it's about what AI has access to when it answers.

Here are the four moves that transform AI outputs:

Move 1: Feed Documents, Not Descriptions

Don't describe what you want AI to know. Give it the actual source material.

❌ Weak approach:

"Analyze our client's pain points. They're a mid-sized manufacturing company struggling with operational efficiency."

✅ Strong approach:

Upload three files:

The client's current state process documentation
Your business capability framework
Interview transcripts from stakeholder conversations

Then prompt: "Using the uploaded process documentation and interview transcripts, map each pain point to the relevant business capability in the framework. Flag any pain points that don't cleanly map to a single capability."

Why this works: AI isn't guessing what "operational efficiency challenges" look like. It's extracting actual pain points from real documents and applying your specific framework.

Move 2: Provide Style Examples, Not Style Instructions

Don't tell AI how to write. Show it examples of your previous work.

❌ Weak approach:

"Write in a professional consulting tone that's authoritative but accessible."

✅ Strong approach:

Upload 2-3 of your best previous deliverables (capability assessments, strategic recommendations, executive summaries) and prompt: "Analyze the writing style, structure, and level of detail in these three examples. Then draft the new capability assessment using the same style, formatting conventions, and analytical depth."

Why this works: "Professional consulting tone" means different things to different people. Your actual work is an unambiguous reference point. AI can pattern-match against concrete examples far better than it can interpret abstract style guidance.

Move 3: Embed Rules and Policies Directly

Don't rely on AI's judgment. Give it explicit rules, constraints, and decision criteria.

❌ Weak approach:

"Recommend the top three strategic opportunities for this client."

✅ Strong approach:

Create a rules document that includes:

Your prioritization criteria (alignment to North Star vision, quantifiable ROI, implementation feasibility)
Client-specific constraints (budget ceiling, regulatory requirements, cultural readiness)
Your firm's methodology (how you assess maturity, how you calculate business value)

Upload this alongside the analysis data, then prompt: "Using the prioritization criteria in the rules document, evaluate each strategic opportunity and rank the top three. Show your scoring for each criterion."

Why this works: You've eliminated ambiguity. AI isn't making subjective judgment calls—it's applying your explicit decision framework.

Move 4: Use Structured Data to Eliminate Hallucinations

When accuracy matters, feed AI structured data (spreadsheets, databases, JSON) instead of asking it to synthesize from unstructured text.

❌ Weak approach:

"Based on general industry trends, estimate the cost savings from consolidating these three capabilities."

✅ Strong approach:

Upload a CSV with:

Current state costs per capability
Headcount allocated to each capability
Processing volumes and error rates
Industry benchmarks for consolidated operations

Then prompt: "Using only the data in the uploaded CSV, calculate the projected cost savings from consolidating Capabilities A, B, and C. Show the calculation for each cost category."

Why this works: AI has a concrete, unambiguous reference point. It's not generating "reasonable-sounding" numbers from its training data—it's performing calculations on actual client data. Hallucination risk drops to near zero.

The Three Layers of Context

Effective context engineering means orchestrating three types of information:

Instructional Context: The task definition, format requirements, and success criteria

Knowledge Context: The documents, examples, frameworks, and data AI needs to complete the task

Tool Context: External systems AI can access (APIs, databases, knowledge graphs)

Most people focus exclusively on instructional context (the prompt). High performers layer in rich knowledge context and, where appropriate, tool context to ground AI's responses in verifiable information.

Real-World Example: From Garbage to Gold

Here's how I applied this framework to transform a failing AI workflow:

The Task: Generate a capability maturity assessment for a financial services client.

My First Attempt (Prompt-Heavy, Context-Light):

"You are an expert business architect. Analyze the client's operational processes and create a capability maturity assessment. Use a 5-level maturity model. Focus on digital capabilities and identify gaps."

Result: Generic, unactionable output that could apply to any financial services company. No client-specific insights.

My Second Attempt (Context-Engineered):

Uploaded files:

Client's process documentation
My capability framework with detailed maturity level definitions
Two previous maturity assessments I'd done for similar clients (as style/format examples)
A CSV with the client's current technology stack, headcount per function, and key performance metrics

Prompt:

"Using the uploaded process documentation and performance data, assess the maturity level of each capability in the framework. Follow the structure and analytical approach shown in the example assessments. For each capability rated below Level 3, cite specific evidence from the process documentation explaining the gap. Format the output as a markdown table with columns: Capability, Current Maturity Level, Evidence, and Gap Description."

Result: A client-ready assessment that required only minor edits. It cited specific processes from their documentation, used our firm's maturity definitions precisely, and matched the tone and structure of my previous work.

Time saved: Approximately 4 hours of manual analysis and writing.

Common Context Engineering Mistakes

Even when people grasp the concept, they make predictable errors:

Mistake 1: Uploading irrelevant documents

More context isn't always better. If you upload 50 files, AI struggles to identify what's relevant. Be selective. Include only the documents that directly inform the task.

Mistake 2: Assuming integration is automatic

Just because you uploaded a capability framework doesn't mean AI will apply it correctly. You need to explicitly instruct AI how to use each piece of context: "Map every pain point to a capability in the uploaded framework. If a pain point doesn't fit, flag it as 'Uncategorized.'"

Mistake 3: Accepting outputs without verification

Context engineering dramatically improves accuracy, but it doesn't guarantee perfection. Always verify that AI used the right source material and applied your rules correctly. Ask it to cite specific pages or data points so you can trace its reasoning.

The Strategic Shift: From Linguistic Tricks to Information Architecture

Here's the mindset shift that separates context engineers from prompt engineers:

Prompt engineers ask: "What words will make AI give me the output I want?"

Context engineers ask: "What information does AI need to produce the output I want?"

Prompting is a creative writing exercise. Context engineering is an information architecture exercise.

As AI models become more sophisticated, they get better at understanding complex instructions without linguistic tricks. But they're still only as good as the information environment you design for them.

Your Action Plan

If you want better AI outputs starting today, follow this sequence:

Step 1: Stop tweaking your prompt. Identify what context is missing.

Step 2: Gather the source materials AI actually needs:

The frameworks and methodologies you use
Examples of your best previous work
Client-specific data and documentation
Explicit rules and decision criteria

Step 3: Structure those materials so AI can use them:

Convert policies into bullet-point rules documents
Extract quantitative data into CSVs
Label your example files clearly ("Example 1: High-quality capability assessment")

Step 4: Write prompts that explicitly reference your context:

"Using the capability framework in Document A…"
"Following the style and structure shown in Example 1…"
"Applying the prioritization rules in the uploaded rules document…"

Step 5: Verify outputs by checking that AI actually used your context correctly. Ask it to cite sources, show calculations, or explain which rule it applied.

The Bottom Line

You can't prompt your way to great outputs if the context is weak. But you can engineer your way to consistently excellent outputs by mastering context.

The business architects and consultants who dominate with AI aren't the ones with the cleverest prompts. They're the ones who've built libraries of frameworks, examples, templates, and rules that they systematically feed into AI's context window.

They've shifted from asking "How do I phrase this better?" to "What information does AI need to produce this deliverable at my quality standard?"

That shift—from linguistic creativity to information architecture—is what separates AI users from AI masters.

Stop perfecting your prompts. Start engineering your context.

What's the biggest context gap you've discovered in your AI workflow? Have you found that feeding better inputs beats crafting better prompts? Drop your experience in the comments.

SHORT SUBSTACK NOTE:

I spent 2 hours perfecting my prompt. The AI output was still garbage.

Then I changed one thing: Instead of describing what I wanted, I uploaded the actual documents, frameworks, and examples.

The output went from unusable to client-ready in one attempt.

Here's what I learned: You can't prompt your way out of a context problem.

Organizations implementing context engineering are seeing:

→ 90-95% accuracy improvements

→ 40% cost reduction

→ 3x faster deployment

The difference isn't better prompts. It's better inputs.

The 4 moves that transform AI outputs: https://open.substack.com/pub/cupofwit/p/how-to-engineer-better-inputs-the?r=59sawq&utm_medium=ios&shareImageVariant=overlay

LINKEDIN POST:

I wasted 2 hours crafting the perfect prompt.

The AI output? Still garbage.

I tried everything:

→ Chain-of-thought reasoning

→ Few-shot examples in the prompt

→ Role-playing ("You are an expert business architect...")

Nothing worked.

Then I stopped tweaking the prompt and changed the inputs.

Instead of asking AI to "analyze operational pain points," I uploaded:

The actual process documentation (40 pages)
Our capability framework
Three examples of previous analyses
Client-specific performance data (CSV)

The output went from unusable to client-ready. In one attempt.

Here's the lesson: You can't prompt your way out of a context problem.

Recent research from Anthropic confirms this: "Building with language models is becoming less about finding the right words for prompts, and more about architecting the context in which those prompts operate."

The data backs it up:

→ 90-95% accuracy improvements with context engineering

→ 40% reduction in operational costs

→ 3x faster AI deployment to production

The problem isn't your prompt. It's your inputs.

Most people focus on how they ask AI questions (prompt engineering).

Top performers focus on what information AI has access to (context engineering).

The 4 context moves that beat better prompts:

✓ Feed documents, not descriptions (upload actual source material)

✓ Provide style examples, not style instructions (show, don't tell)

✓ Embed rules and policies directly (eliminate subjective judgment)

✓ Use structured data to eliminate hallucinations (CSVs over prose)

Example:

❌ Weak: "Write a capability assessment in a professional tone"

✅ Strong: Upload your capability framework + 2 previous assessments + client data, then prompt: "Following the structure in Example 1, assess maturity using the uploaded framework and cite evidence from the client data CSV"

Same AI. Completely different result.

I wrote the full framework for engineering better inputs—including real examples of context-heavy vs. prompt-heavy workflows:

📖 [Your Substack URL]

Question: What's the biggest context gap you've discovered in your AI workflow? Are you spending more time perfecting prompts or improving inputs?

Here's a shorter LinkedIn post:

I wasted 2 hours perfecting my prompt. The AI output was still garbage.

Then I stopped tweaking the prompt and changed the inputs.

Instead of asking AI to "analyze operational pain points," I uploaded:

Actual process documentation (40 pages)
Our capability framework
Three previous analysis examples
Client performance data (CSV)

The output went from unusable to client-ready. In one attempt.

Here's the lesson: You can't prompt your way out of a context problem.

Recent Anthropic research confirms: "Building with AI is becoming less about finding the right prompt words, and more about architecting the context."

The results:

→ 90-95% accuracy improvements

→ 40% cost reduction

→ 3x faster deployment

The 4 context moves that beat better prompts:

✓ Feed documents, not descriptions

✓ Show examples, don't explain style

✓ Embed rules directly (eliminate guesswork)

✓ Use structured data (CSVs beat prose)

Most people obsess over prompts. Top performers engineer context.

Full framework with real examples: [Your Substack URL]

What's your biggest AI context gap? Are you perfecting prompts or improving inputs?

This version cuts ~40% of the length while keeping the core story, data points, and call-to-action.

All three pieces are ready to go! Just add your Substack URL to the note and LinkedIn post.