“The feature is 90% complete” sounds close to the finish line. For SIers, CTOs and DX leaders in Japan, however, it leaves important questions unanswered: what works, what has been checked and what could still affect delivery?
When working with an offshore team, agree on how to describe progress using results that can be examined. Percentages can still support summaries, but they need clear definitions and evidence.
1. Define completion for each type of work
Before starting, establish completion conditions suited to the task. For design, that might mean a reviewed document with outstanding questions resolved. For a feature, distinguish implementation complete, internal testing complete, integration verified and ready for customer review.
Do not compress these states into a single “done” label. If customer confirmation is pending, show the affected scope and identify which work the development team can still continue.
2. Connect status to concrete results
Each report item should identify scope, status, evidence and remaining work. Evidence might include reviewed documents, test results or a working version in an agreed environment. Include the version and verification date to avoid comparing different states.
If a demo uses sample data or simulated connections, state those limitations explicitly. Readers who did not attend the demonstration should still understand exactly what has been verified.
3. Hypothetical example: the screen works, integration is unverified
An offshore team reports an order inquiry feature as 90% complete. The screen looks polished, but it uses sample data; the connection to the warehouse system has not been tested.
A clearer report would say: the interface has been checked with sample data; warehouse integration remains unverified; the Japanese contact needs to confirm the connection environment; the development team will test integration once that environment is ready. The completion forecast should state this dependency.
This helps the PM identify the decision or support needed, instead of assuming that the entire feature is nearly ready for delivery.
4. Separate results, forecasts and decisions
Results describe what has happened. Forecasts describe expected completion and the assumptions behind it. Items requiring a decision should identify an owner and a requested response date.
When new information arrives, update the forecast and explain the change. If scope grows, preserve visibility of the original scope and additions. Avoid changing completion percentages without explaining that the calculation basis has changed.
5. Use meetings to resolve uncertainty
Share a short report before the meeting. In Japan–Vietnam discussions, prioritize newly verified results, blocked work and options that need agreement. Afterwards, record decisions and action owners where the work is tracked.
Management reports do not need every technical detail. They need enough information for accountable people to decide at the right time and trace the evidence when necessary.
Clarify delivery tracking with TECHNEST
TECHNEST has years of experience working with the Japanese market, designing and developing business systems, modernizing legacy systems and collaborating with Japanese consulting partners.
When discussing a project, define completion, evidence to share and how to address pending items together. Explore our software outsourcing services or contact TECHNEST to discuss a suitable way of working.
