Preventing Miscommunication: The 'I'll Check' Pitfall

This section demonstrates through concrete examples what serious problems vague "I'll check" responses cause in actual business operations.

In a website development project, the client responded with "I'll check about the logo placement." Freelance designer A paused work and moved on to other projects. A week later, the client contacted him saying, "The logo is fine in its current position."

However, what was discovered at the delivery stage was that the client had been checking internally about "logo size" rather than "logo placement position." As a result, changes to the placement position required an additional 8 hours of modification work, and the delivery was delayed by 3 days.

This case demonstrates the ambiguity inherent in the phrase "I'll check." The client failed to clarify "what they were checking," and the contractor didn't specifically ask about "the subject and scope of verification." It was the result of lacking basic communication to prevent miscommunication between both parties.

In another case involving system development, the client responded "I'll check the specifications," and the developer waited for specification confirmation. Two weeks later, the client contacted them saying "The specifications are fine," but in reality, the client had only checked "screen layout" and hadn't verified "database specifications" or "API specifications" at all.

When development proceeded, major specification changes became necessary at the database design stage, and the work hours expanded to 1.8 times the original estimate. Regarding these additional hours, the client argued "We should have confirmed this initially," while the contractor countered that "the verification scope was unclear."

Common to these cases is the lack of clarification regarding the "subject," "scope," "deadline," and "reporting method" of verification. The response "I'll check" sounds cooperative and responsible, but it actually plants seeds for future trouble.

The most important method for alignment is specifying verification items. Unless "what," "by when," and "in what form" verification will be conducted is clarified, preventing communication mistakes becomes impossible.

This section analyzes why information gaps between contractors and clients and organizational factors make miscommunication likely to occur.

First, information gaps between contractors and clients are a fundamental problem. Clients are familiar with their company's business flow and decision-making processes, but contractors cannot see these details. Even when told "I'll check," contractors don't know who within the organization will verify with what criteria and what level of authority.

Conversely, contractors understand technical constraints and work processes, but clients don't fully grasp this expertise. When responding "I'll check," clients often don't adequately consider how verification results will affect the contractor's work.

Next is the complexity of organizational decision-making structures. In client companies, even when a representative says "I'll check," the actual decision-maker is often someone else. There may be an approval flow from representative → manager → executive, but these details aren't conveyed to contractors.

It's also common for verification processes to span multiple departments. Design, marketing, and legal departments each review from different perspectives, but the response "I'll check" makes it unclear which department is checking from which perspective.

Time pressure also contributes to miscommunication. Under tight schedules, clients respond "I'll check for now," and contractors proceed without pursuing details. This accumulation of "for now" responses creates major misalignments later.

The characteristics of communication tools also have an impact. "I'll check" in emails or chat differs from face-to-face communication in that expressions and tone of voice cannot be read to infer details. Text-only information makes it difficult to convey the urgency or importance of verification.

Furthermore, differences in perception about how to share verification results are problematic. Clients think reporting the fact that they "verified" is sufficient, but contractors want to know detailed content and background of the verification. This gap in expectations makes it difficult to prevent miscommunication.

The ambiguity of responsibility scope is also a factor that cannot be overlooked. When it's unclear how much responsibility the representative who said "I'll check" bears for verification results, the location of responsibility becomes ambiguous when problems arise later.

This section shows practical procedures for converting "I'll check" into specific, actionable agreements.

Step 1: Specifying verification items

When told "I'll check," contractors must always clarify the following elements:

• Verification subject: Specifically identify "which part of the design to verify" or "which specification items to check"
• Verification scope: Clarify whether it includes "layout only or colors too" or "functional aspects or just appearance"
• Verification perspective: Identify whether it's "consistency with brand guidelines," "technical feasibility," or "budget considerations"

For example, instead of "I'll check the logo," specify "I'll check the logo's placement position, size, and color from the perspective of consistency with brand guidelines."

Step 2: Visualizing the verification process

Clients should specify the verification procedure and stakeholders.

• Verifiers: "Who makes the final decision" and "who coordinates when multiple departments are involved"
• Verification procedure: Clear approval flow like "representative → manager → executive"
• Judgment criteria: Advance sharing of "what criteria will be used to judge approval or rejection"

Actual description example: "Design manager (Tanaka) conducts initial verification, then marketing manager (Sato) gives final approval. Judgment criteria are brand guideline compliance and feasibility within budget."

Step 3: Setting deadlines and reporting methods

Convert vague "I'll check" into deadline-bound agreements.

• Verification deadline: Specific date and time setting like "by ○ month ○ day ○ o'clock"
• Interim reporting: "Progress report on ○ day" or "contact timing if problems arise"
• Reporting method: "Written response via email," "explanation in online meeting," or "key points report via chat"

Description example: "Verification completed by March 15, 5 PM. If there are progress issues, interim report by March 13, 12 PM. Results will be provided in detailed written email response, with online meeting for additional explanation if necessary."

Step 4: Documentation rules for verification results

As a method for alignment, agree in advance on how to record verification results.

• Record items: "Verification items," "verification results," "judgment reasoning," "conditions or constraints," "next actions"
• Sharing method: "Formal notification via email," "recording in project management tools"
• Agreement confirmation: "Response confirming understanding from contractor," "questions within ○ hours if there are doubts"

Step 5: Pre-agreement on exception handling

Set rules for when unexpected situations occur during the verification process.

• Conditions for deadline extension: "Under what circumstances deadline extension is possible"
• Escalation: "Routes for consulting superiors when judgment is difficult"
• Alternative proposal presentation: "Method for presenting alternatives when original proposal is not approved"

These procedures significantly improve communication mistake prevention. The key is agreeing on these procedures at project start and documenting them in project charters or contracts.

Implementation points

Even for small projects, always clarify at minimum the three points: "what," "by when," and "how to report." For large projects, create dedicated checklists for each verification item and manage progress.

Also, always record verification results in writing, with both parties holding the same documents. Verbal verification doesn't leave records and becomes a source of future miscommunication.

This section specifically lists patterns of miscommunication that contractors and clients commonly fall into.

Typical pitfalls for contractors

The assumption that "it's safe because it's being verified" is the most dangerous. The moment a client says "I'll check," contractors have the illusion that the problem is moving toward resolution. However, in reality, verification work often hasn't even begun.

Omitting technical details in explanations is another frequent pitfall. When a client says "I'll check about responsive support," contractors need to explain down to "CSS media query implementation details," "breakpoint settings," and "display verification scope for each device." Clients who don't understand technical backgrounds are likely to conduct only superficial verification.

Also, reluctance to remind about verification deadlines is problematic. Consideration like "I think you're busy" or "I'm sorry to rush you" ultimately causes delays for the entire project. Deadline management is an important responsibility of contractors.

Furthermore, accepting ambiguous responses to verification results is common. Misinterpreting ambiguous responses like "Basically no problem," "Generally approved," or "Let's adjust the details later" as clear approval.

Typical pitfalls for clients

Not communicating the complexity of internal coordination to contractors is the biggest problem. While saying "I'll check," multiple department coordination is actually necessary, with each checking from different perspectives. However, not explaining this complexity to contractors causes them to misunderstand it as simple verification work.

Not properly setting priority for verification work internally is another frequent pitfall. Even urgent verification items for contractors are treated as low priority within the client organization. This temperature difference causes deadline delays.

Also, representatives without verification authority responding "I'll check" is problematic. Even though actual decision-makers are different, window representatives easily respond "I'll check," leading to rejections from superiors later.

Conveying verification results only partially is also dangerous. Even when internal conclusions are "conditional approval" or "partial modifications needed," only "approved" is conveyed to contractors. Since condition details or modification points aren't conveyed, later rework occurs.

Common pitfalls for both parties

The misunderstanding that "verification = approval" is the most deep-rooted problem. Verification work is checking facts and consistency, and doesn't necessarily mean approval. However, both parties tend to perceive completion of verification work as synonymous with approval.

Failing to document is also a common problem. Even for important verification items, they settle for simple verbal or chat exchanges. This becomes the cause of "he said, she said" disputes later.

Also, not sharing assumptions for verification is common. Clients verify based on their company circumstances, while contractors explain based on technical constraints. This difference in assumptions creates different interpretations of verification results.

Differences in perception about deadlines cannot be overlooked either. A client's "I'll check" means "take time for internal coordination and verify carefully," but contractors often interpret it as "results will come within a few days."

Practical measures to avoid pitfalls

To avoid these pitfalls, always create a "verification checklist" when verification items arise. Record verification subjects, deadlines, stakeholders, reporting methods, and judgment criteria, and agree between both parties.

Also, mandate regular interim reports about verification work progress. Always include verification work status in weekly progress reports.

Most importantly, don't use the phrase "I'll check." Instead, use specific expressions like "Regarding ○○, by ○ day, from the ○○ perspective, I'll consider and convey results via ○○ method."

Practical improvements to prevent miscommunication can be implemented immediately starting today. Here are specific actions both contractors and clients should change in tomorrow's communication.

Actions contractors should practice starting today

First, develop the habit of always asking three questions the moment you hear "I'll check." "What will you verify?" "By when can I receive results?" "In what form will you convey results?" These three questions can convert vague verification into concrete promises.

Next, when making proposals yourself, organize and convey information in an easily verifiable format. "I've created three design pattern options. Pattern A excels in ○○ perspective, Pattern B has ○○ merits. Could you verify which to adopt by ○ day?" is a specific proposal method.

Also, create a "verification status management table" for projects waiting for verification and update it daily. Record project names, verification items, deadlines, current status, and next actions. This prevents verification oversights and deadline overruns.

Actions clients should practice starting today

Prohibit "I'll check" responses internally and standardize alternative expressions. Mandate responses in the format "Regarding ○○, ○○ department will consider by ○ day and convey results via email."

Disclose internal verification processes to contractors. Convey information like "Our verification has three stages: representative verification → manager approval → executive decision. Usually requires ○ days" at project start. This enables contractors to schedule appropriately.

Create verification result reporting templates to convey necessary information without omission. Always include five items: "verification items," "verification results," "judgment reasoning," "conditions/constraints," and "next required actions."

Actions both parties should jointly undertake

Create a "communication agreement" at project start. Document procedures when verification items arise, deadline setting methods, reporting formats, and escalation procedures, and agree between both parties.

Always include verification pending items as agenda items in weekly regular report meetings. Share verification progress status, expected completion timing, and factors creating obstacles, considering countermeasures as necessary.

Also, conduct "communication retrospectives" after project completion. Organize cases where miscommunication occurred, verification processes that worked well, and points for improvement, utilizing them in next projects.

Specific tool utilization

As a method for alignment, utilize project management tools. Register verification items as "tasks," specifying assignees, deadlines, and detailed descriptions. When verification is completed, record results in comment sections for all stakeholders to view.

In chat tools, create "verification-only channels" to consolidate verification exchanges. For important verification results, always provide formal email responses after chat notifications.

Continuous improvement

Communication mistake prevention isn't completed with one-time improvement. Monthly compilation of "miscommunication occurrence count," "verification deadline compliance rate," and "verification result documentation rate" provides numerical understanding of improvement status.

Review communication methods between contractors and clients every three months to discover new challenges and improvement points. Continuously evolve communication methods according to industry trends and tool advances.

Preventing miscommunication isn't a temporary measure but the foundation for long-term trust building in contractor-client relationships. The accumulation of small improvements practiced from today leads to avoiding major troubles tomorrow. Contractors should practice specifying verification items, and clients should practice transparency in verification processes, starting from tomorrow's communication.