SHARE-ME GUIDE

A 30-Day Implementation Plan to Test Business Card Management with a Small Team | Template for Recording Results and Deciding Whether to Continue

Share-Me |

Conceptual diagram of an implementation roadmap showing four stages: preparing business cards, checking them, piloting with the team, and evaluating results

When introducing business card management, collecting everyone's past business cards from the start can result in the evaluation period ending before you even finish entering them. First, focus on one team and one business task, and create a plan to confirm whether the registered information can be used for the next job.

This article outlines a 30-day pilot plan for a small group. The 30-day period is a suggested timeframe for observing operations and does not indicate Share-Me's free trial period or contract terms. It does not guarantee increased sales or reduced working time, but introduces a method for recording results so you can decide whether to continue, make adjustments, or discontinue the pilot.

Define the Scope of the Pilot Before Starting

"Making business card management more convenient" is too broad to use as a basis for evaluation. Choose one specific task to test, such as "Checking the contact information of a recent business meeting participant even when the person in charge is away." Participants should include not only those who register information, but also those who refer to it and the person responsible for evaluating the results. It is also important not to form the team only with people who are good at using the software.

Pre-Start Planning Card

  • Problem to Solve: [One specific business situation where you have actually faced difficulties]
  • Participants and Roles: [Person who registers / Person who refers / Support person / Person responsible for evaluation]
  • Target Information: [New cards exchanged during the pilot, cards for a specific project, etc.]
  • Out of Scope: [Migrating all past business cards, integrating with external systems, etc.]
  • Duration: [Start date / Midpoint check date / Final decision date]
  • Available Budget and Work Allocation: [Contract cost / Time allocated for preparation and daily operations]
  • Conditions for Discontinuation: [Unexpected public disclosure, serious information errors, etc.]

Complete the product contract, account setup, and internal approval before starting. If you cannot confirm a secure storage location and viewing scope for real data, first verify the procedures using dummy data. Record the results of the mock exercise and the results of actual business use separately.

If organizing past business cards is not the purpose of the pilot, keep the volume of cards entered at the start to the bare minimum. Refer to the procedure for gradually digitizing accumulated paper business cards when selecting target cards, and narrow the scope to match what you want to confirm in this pilot.

30-Day Implementation Schedule

The following schedule is a suggestion for you to adjust internally. Arrange it according to holidays and the frequency of exchanging business cards, and do not include days when setup is still underway in the evaluation of regular operations.

Days 1–3: Record Current Workflows

Record situations where you search for contact information using conventional methods, check with the person in charge, or transcribe information. Record not only successful situations but also times when you had to ask the person again. Define the boundaries from start to finish, and distinguish waiting time from actual working time.

What to Record:Current procedures, number of cases, difficult situations, and issues to use for comparison. This provides a basis for evaluation so you do not judge it as "faster" based only on past impressions.

Days 4–7: Complete One Cycle from Registration to Reference

Register the target business cards and match the company name, name, and contact information with the original information. Confirm whether another participant can find the same person within the permitted scope. If a support person operates the software on their behalf, record this separately from results achieved independently.

What to Record:The first point where you got stuck, points where the explanation was insufficient, and confirmed procedures. Revise the explanation on Day 7 and add the date of the change.

Days 8–14: Use in Daily Workflows

Incorporate it not only into special group work days but also into regular timings such as after visits or online meetings. Do not stop at registration; refer to the information when contacting the person next. On days when no cards were exchanged, record "No target" and distinguish this from "Unregistered."

What to Record:Number of cards registered, number of confirmations completed, situations where information was actually referred to, and time spent asking questions and providing support. On Day 14, rather than adding new features, check whether the target business task was completed from start to finish.

Days 15–21: Reconfirm Difficult Situations

Revisit people who could not be found in the first half or information that took a long time to confirm. Categorize the causes as "Input content," "Understanding of procedures," "Selection of targets," or "Required features and terms of use," and narrow down the points to change at once.

What to Record:Causes, corrections made, results of reconfirmation, and remaining issues. If a support person accompanied the user constantly only in the second half, also record that support burden.

Days 22–30: Decide Whether to Continue

Use the revised procedures in regular business from Days 22–27. On Days 28–30, compare user feedback with the records and have the person responsible make a decision. If there were few card exchanges and no verification situations, do not decide it as good or bad, but rather as "Insufficient information for judgment."

What to Record:Basis for the decision, unverified conditions, the next target, and the person responsible. Do not make company-wide rollout an automatic next step; confirm the necessary approvals and preparations separately.

Verification Records to Keep for Each Case Can Be Short and Single-Page

Creating detailed daily reports can make the recording itself a burden. Record one case at a time using the following items, and arrange for personal information to refer to existing approved records. There is no need to duplicate business card images or contact information into the evaluation document.

Verification Log Template

  • Date / Person in Charge / Procedure Version: [Enter]
  • Situation: [Whose business task it was needed for]
  • Target: [Identification information such as a project number]
  • Result: [Completed / Completed with support / Incomplete / No target]
  • Burden: [Actual working time spent on registration, confirmation, searching, and support]
  • Waiting Time: [Reason and duration. Distinguish from actual working time]
  • Problem and Next Action: [Possible cause / Person in Charge / Confirmation Date]

For weekly checks, record not only the percentage but also the denominator and numerator. "Number of confirmations completed ÷ Number of registration targets this time" is an example calculation to see progress, but define it so that cards excluded from the target are not included in the denominator. Also, even if a card can be registered, the goal is not achieved if it cannot be used later. Evaluate "Whether other staff members could confirm the necessary information" separately.

Example of a Fictional Record: Search Was Successful, but Additional Confirmation Was Needed

The following is a fictional example for explanation purposes and is not based on actual measurements or Share-Me implementation cases. Suppose Person B found the contact information for Project X but did not know who would make the next contact and checked with Person A. Record the result as "Completed with support" and the problem as "Next person in charge unknown." Do not assume it is a search function failure, but instead review where the necessary business information is stored.

If the conversation recording items were insufficient, you can refer to the template for notes after exchanging business cards. Instead of copying the entire conversation into the pilot log, record which items were missing to provide material for improvement.

Set Criteria for Continuing, Making Adjustments, or Discontinuing Before Starting

To prevent choosing a convenient criterion on the final day, distinguish "Conditions that must be met" and "Conditions that would be good to improve" at the planning stage. Also, set the upper limits for costs and operational burden according to your company's workload. There is no need to borrow general success rates or other companies' time savings as your company's passing criteria.

  • Continue:The intended business task was confirmed, essential terms of use were met, and there is a person responsible who can take on the daily confirmation and support burden.
  • Revise and Re-evaluate:There is a possibility it meets the purpose, but there are issues with procedures or explanations that can be corrected. Decide on the corrections, the situation to re-evaluate, and the decision date.
  • Discontinue / Consider an Alternative:It does not meet the necessary sharing conditions, serious issues cannot be resolved, or the costs and ongoing burden exceed the approved limits.
  • Defer Decision:The target business task did not occur, and there is insufficient evidence. Clearly state the missing situations and observation period, and do not extend it indefinitely.

If a discontinuation condition such as an unexpected public disclosure occurs, stop the target task without waiting for Day 30 and report it to the person responsible. It is important not to offset the evaluation of convenience with the confirmation of whether information can be handled appropriately.

What to Hand Over to the Next Person at the End

Finally, summarize the purpose, target, verified situations, decision, and remaining issues on a single page, rather than just an impression that it "went well." Distinguishing the time spent on initial setup and explanation from the time that will continue to occur when continuing makes it easier to estimate the burden of expanding it to the next participant. Also, confirm how data retention, deletion, and contracts will be handled when ending use, in accordance with company policy and terms of use.

If there is still a scope where paper business cards are used in parallel, also organize the operation of using paper and digital business cards together. The conclusion of the pilot is not a guarantee that the same results will be achieved company-wide, but material for deciding the next target and verification conditions.

Official Information Referenced

With Share-Me, You Can Consult About Corporate Use Starting from the Business You Want to Test

Share-Me's corporate guide includes AI scanning of paper business cards, visualization of contacts within the team, and creation and editing of account information by administrators. First, write "Who registers and who confirms what" on the planning card, and let's consult about the situations you want to verify.

The 30 days in this article is our own operational plan. Please confirm the eligibility of the pilot, pricing, number of users, specific scope of permissions, and handling of data at the end individually. Check Share-Me's corporate plan and consult about implementation conditions

Product information confirmation date: October 29, 2026. Actual operations in the management screen and effect measurements have not been performed.

Back to blog