Chapter 2: Identifying Achievements Across a Complex Enterprise
Large organizations generate meaningful accomplishments throughout the year, but many of these achievements are never documented. They may remain hidden in departmental reports, regional presentations, project dashboards, customer feedback, or conversations between managers. In a complex enterprise with multiple divisions, subsidiaries, locations, and specialized functions, finding important corporate success stories requires a systematic discovery process.
Without such a process, enterprise recognition often favors the most visible executives, products, or departments. Meanwhile, smaller teams and regional offices may produce measurable business value without receiving appropriate attention. Enterprise achievement management creates a structured way to identify accomplishments wherever they occur.
Establish an Enterprise-Wide Discovery Process
The first step is to assign responsibility for achievement discovery. Depending on the organization, the process might be coordinated by corporate communications, human resources, strategy, program management, employee recognition, or another central function. A cross-functional committee may be useful when no single department has visibility across the entire enterprise.
The process should define how often achievements will be collected, who can submit them, what information is required, and how potential stories will be evaluated. Monthly submissions and quarterly reviews can prevent organizations from trying to reconstruct an entire year of activity immediately before an annual report, leadership meeting, or award deadline.
A standardized submission form can request:
- The problem, need, or opportunity addressed
- The action taken and people involved
- The relevant dates and locations
- Baseline conditions and intended measures
- Quantitative and qualitative results
- Stakeholders who received value
- Available supporting evidence
- Required approvals or confidentiality restrictions
At this stage, submissions do not need to be polished narratives. The objective is to capture potentially valuable information before records are lost or team members move to other responsibilities.
Review Every Part of the Organization
Discovery should extend across divisions, departments, subsidiaries, business units, facilities, and corporate functions. Each area creates different forms of value.
Finance may improve forecasting, reporting accuracy, cost control, or working-capital management. Operations may reduce defects, downtime, processing time, or resource use. Human resources could strengthen recruitment, development, retention, accessibility, or employee well-being. Technology teams may improve cybersecurity, automate a process, modernize infrastructure, or increase system reliability.
Sales and marketing can document market expansion, customer acquisition, campaign performance, or partner development. Customer service teams may improve satisfaction, response time, resolution rates, or accessibility. Legal and compliance departments might reduce risk, improve governance, or create more efficient review processes. Supply-chain teams can strengthen resilience, delivery performance, sourcing, or inventory management. Research groups may produce discoveries, prototypes, patents, testing advances, or commercially valuable innovations.
These departmental achievements should be evaluated according to their objectives and context. Applying the same performance measures to every function would overlook the different ways each contributes to organizational success.
Include Regional and International Offices
Important business-unit accomplishments frequently emerge outside corporate headquarters. Regional teams may understand local customers, regulations, cultures, infrastructure, and market conditions better than centralized departments. Their work can reveal valuable approaches that are not immediately visible to global leadership.
The discovery process should include designated contacts within regional and international offices. Submission materials may need translation, and evaluators should consider local context when reviewing results. A revenue figure that appears modest at the enterprise level may represent substantial growth in a developing market. A process improvement in a remote facility may overcome infrastructure or logistical challenges not encountered elsewhere.
Regional offices should also be able to explain local achievements in their own terms rather than being required to fit every accomplishment into a headquarters-centered narrative.
Invite Managers and Employees to Participate
Senior leaders should not be the only source of corporate success stories. Employees closest to customers, products, systems, and operations often recognize improvements that executives do not see.
Organizations can invite managers and employees to submit potential stories through internal forms, team meetings, employee portals, recognition programs, or periodic campaigns. Managers should be encouraged to ask questions such as:
- What problem did our team solve?
- What process works better than it did previously?
- What measurable customer or employee benefit did we create?
- What difficult milestone did we reach?
- What did another department adopt from our work?
- What result would be lost if we failed to document it?
Participation should be easy and psychologically safe. Employees may hesitate to propose their own achievements if they believe doing so appears self-promotional. Leaders can address this concern by presenting submissions as organizational learning and fair attribution rather than personal boasting.
Use Information the Enterprise Already Collects
Achievement discovery does not always require new reporting systems. Large organizations already produce performance reviews, project completion reports, operational dashboards, audit findings, employee surveys, customer data, research summaries, and leadership presentations. These materials can reveal improvements, milestones, and unexpected results.
Leadership meetings can include a recurring achievement-review item. Project closeout procedures can ask whether the work produced a documentable accomplishment. Performance reviews can identify employee achievements that also demonstrate team or departmental value. However, information should be verified and approved before it is used externally.
Recognize Collaboration Fairly
Many employee achievements depend on cross-functional or cross-border collaboration. A new product might involve research, engineering, design, legal, marketing, operations, and customer service teams across several countries. The final story should identify the principal contributors without implying that one highly visible department produced the result alone.
Clear attribution protects credibility and supports employee recognition. It also helps the organization understand how collaboration created value.
Apply Consistent Evaluation Criteria
To prevent larger or more visible groups from overshadowing smaller teams, enterprises should evaluate every potential achievement using consistent questions:
- Was there a clearly defined challenge or opportunity?
- Did the work exceed routine expectations?
- What actions were taken?
- What scale and complexity were involved?
- Who benefited?
- Are the results measurable and attributable?
- Is credible evidence available?
- Can the information be disclosed responsibly?
A smaller departmental achievement may be more compelling than a heavily promoted enterprise initiative if it produced clearer and better-supported results. By creating an inclusive and evidence-based discovery process, large organizations can uncover business-unit accomplishments, departmental achievements, and employee achievements that deserve to be preserved and communicated.
Selected accomplishments may also be suitable for external recognition. Organizations can explore current Globee Awards programs, categories, eligibility requirements, achievement periods, nomination rules, and deadlines at GlobeeAwards.com.