There is a small, four-letter word that tends to create rather massive problems inside organizations. It shows up in emails, meetings, and casual conversations, often masking enormous complexity with a dangerous illusion of simplicity.

That word is “just.”

You hear it all the time, in various forms:

• “Can you just update the website?”
• “Let’s just build a new feature for that.”
• “Why don’t we just add AI to our product?”
• “It should be easy. We just need a new report.”

The word “just” makes complex work sound simple. When that happens, expectations become disconnected from reality. Over time, this gap leads to missed deadlines, frustrated teams, and projects that grow far beyond what anyone originally imagined. This seemingly harmless word can become the most expensive one in your business vocabulary.

The Illusion of Simplicity

When a person uses the word “just,” they are typically focused on the desired outcome, not the intricate process required to achieve it. They see the tip of the iceberg, unaware of the massive structure hidden beneath the surface.

Consider a common request from a leader: “Can we just update the homepage?”

What they likely see is a straightforward, three-step process:

1. Change a block of text.
2. Add a new image.
3. Publish the changes.

What the technical and creative teams actually have to manage is a far more extensive list:

• Content Strategy: Is the new messaging on-brand and effective?
• Brand Alignment: Does the new image fit our visual guidelines?
• Accessibility: Does the update meet WCAG standards for all users?
• Mobile Responsiveness: How will this change look on various devices?
• CMS Workflow: Who needs to review and approve this content before it goes live?
• Image Optimization: Is the image compressed for fast loading times?
• SEO Implications: Will this change affect our search engine rankings?
• Cross-Browser Testing: Does the update function correctly on Chrome, Safari, Firefox, and Edge?

The visible part of the work is small, but the system behind it is not. As one developer famously joked, “The word ‘just’ usually means the person asking has skipped about 20 steps.”

“Just Integrate Our Product with [Another Product]”

Product and engineering teams hear this version of the request constantly.

A request like:

“Can we just integrate our product with Salesforce?”

or

“Can we just connect our system to HubSpot?”

sounds straightforward. After all, both systems already exist, so how hard could it be?

In reality, a “simple integration” can trigger a cascade of technical and operational work.

That single integration might involve:

• API Research: Understanding the other platform’s API documentation and limitations.
• Authentication & Security: Implementing OAuth, API keys, or other authentication methods securely.
• Data Mapping: Determining how fields and objects map between the two systems.
• Data Transformation: Handling mismatched formats, missing fields, and data validation rules.
• Error Handling: Designing systems to manage failed syncs or partial updates.
• Rate Limits: Managing API call limits imposed by the external platform.
• UI/UX Design: Creating a clear configuration interface for users.
• Quality Assurance: Testing dozens of edge cases and real-world scenarios.
• Documentation: Explaining setup and troubleshooting to customers.

And once the integration ships, the work is far from over.

It now requires ongoing:

• maintenance
• monitoring
• support
• updates whenever the external platform changes its API

A “simple integration” can create years of long-term responsibility for the product team.

As the renowned software engineer Martin Fowler wrote:

“Any fool can write code that a computer can understand. Good programmers write code that humans can understand.”

The part that most people don’t see is the immense effort required to make software integrations reliable, maintainable, and secure over time.

The New Culprit: “Just Add AI”

This is the latest and most pervasive version of the problem. As artificial intelligence becomes more accessible, organizations are eager to integrate it. The suggestion, “Can we just add AI to this?” is now a common refrain in strategic meetings.

But AI projects involve far more than plugging in a tool or calling an API. A successful AI implementation requires a comprehensive strategy that includes:

• Identifying a Valid Use Case: Finding a real business problem that AI can solve effectively.
• Defining Success Metrics: Establishing clear KPIs to measure the AI’s impact.
• Data Management: Identifying, cleaning, and preparing massive datasets for training and operation.
• Workflow Design: Creating new prompts, processes, and human-in-the-loop workflows.
• Output Evaluation: Continuously assessing the quality and accuracy of the AI’s output.
• Privacy and Security: Addressing the significant ethical and compliance considerations of using data.
• System Integration: Connecting the AI model with existing software and platforms.
• User Training: Teaching employees how to use the new tools effectively and responsibly.
• Governance: Creating policies for the ethical and appropriate use of AI.

Adding AI is not merely a technology decision; it’s a fundamental business transformation. As AI researcher Andrew Ng has said, “AI is the new electricity.” It doesn’t just add a feature, but it has the potential to change how everything works. Treating it as a “just” task is a recipe for failure.

Is There A Better Way to Frame Requests?

The word “just” isn’t always used with careless intent. People say it because they are focused on goals, not implementation. Executives think about high-level objectives, managers think about delivery timelines, and specialists think about the detailed execution. The word “just” often appears when someone is looking at the work from a higher, less detailed altitude.

The problem isn’t the word itself, but the underestimation of the systems that underpin modern work. Instead of starting with “just,” a more productive approach is to foster curiosity and collaboration.

Rather than saying, “Can we just add this?” try asking questions that invite a deeper conversation:

• What would it take to do this well?
• What teams and systems would this request affect?
• What are the potential risks or trade-offs involved?
• Is there a simpler, more effective way to achieve the desired outcome?

These questions empower teams to surface hidden complexities before work begins, leading to better planning, more accurate timelines, and more realistic expectations.

Replace “Just” with Curiosity

The real lesson is that modern work, especially in the digital realm, exists within complex, interconnected systems of technology, processes, and people. A seemingly small request can send ripples across these systems in unexpected ways.

The most effective leaders and organizations understand this reality. They replace the dismissive nature of “just” with an inquisitive spirit. They ask questions, listen to their experts, and respect the invisible work that turns great ideas into reality. When you foster a culture of curiosity, projects become clearer, teams become more aligned, and outcomes become far more predictable.

As the famous adage goes, “Everything should be made as simple as possible, but not simpler.” Before you use that four-letter word again, take a moment to consider the vast complexity it might be hiding. The most expensive word is indeed one that makes everything sound simple.