IT Company B's Story: How ZEROCK Changed the Information-Sharing Culture
Introduction: Strong Technical Talent, Broken Information Sharing
Company B is a software development company with 200 employees. Strong engineers, strong technical reputation. But internal information sharing was a serious problem.
"We have no idea what the team next door is working on." "Different teams are solving the same problems." "When an engineer leaves, their knowledge disappears." These voices had become common enough that leadership was genuinely concerned.
This article traces how Company B deployed ZEROCK and transformed its information-sharing culture.
Before Deployment
Scattered Knowledge
Each team at Company B managed information in its own way. Some teams used Confluence, others Notion, others GitHub's wiki. No unified knowledge foundation existed across the company — cross-team information sharing was structurally impossible.
Engineering lead Suzuki (name changed) describes the situation: "When we hit a technical problem, I knew we probably had someone internally who knew the answer — but I had no idea who to ask. We usually ended up researching from scratch and solving it ourselves."
Reinventing the Wheel
The lack of information sharing made "reinventing the wheel" a regular occurrence. A problem one team worked hard to solve was being solved from scratch by another team. This kind of duplication happened routinely.
Looking back afterward, it was common to discover: "that other team had already solved this." Engineers' valuable time was being consumed by redundant work.
Knowledge Siloing
Knowledge was concentrated in specific engineers — specialists in particular systems or domains. When those engineers were available, problems got solved. When they were on leave or had left, operations struggled.
When one veteran engineer left, it took weeks to decode the legacy system specifications that only they had understood.
Struggling with AI adoption?
We have prepared materials covering ZEROCK case studies and implementation methods.
Deploying ZEROCK
What Made the Difference
Several factors led Company B to choose ZEROCK. Cross-source search across existing documents (Confluence, Notion, GitHub, etc.). AI-powered natural-language search — information accessible without thinking up the right keywords. And GraphRAG technology automatically linking related information.
Suzuki's assessment: "Previous tools were just boxes to put information into. ZEROCK goes the step further — it supports actually using what's in there."
Staged Deployment
Company B began with a pilot in the infrastructure team. Infrastructure troubleshooting frequently references past incidents — making ZEROCK's impact easy to observe and measure.
During the pilot, the habit of asking ZEROCK questions like "what caused that incident?" and "how do we configure this server?" took root quickly across the infrastructure team.
What Changed After Deployment
Dramatically Improved Information Accessibility
The most visible change: information accessibility. Information that was previously "I don't know where it is" or "I don't know who to ask" became findable just by asking ZEROCK.
"When a technical question comes up, ask ZEROCK first" became established behavior. New engineer ramp-up time shortened significantly.
Tacit Knowledge Becoming Explicit
Through ZEROCK's AI Knowledge feature, knowledge engineers acquired through daily work began accumulating naturally. Technical discussions in Slack. Code review comments. Incident response logs. All of this flows into the knowledge base automatically, becoming searchable.
Suzuki says: "Veteran engineers' knowledge is naturally becoming company assets. That's the most valuable thing."
Breaking Down Team Silos
Cross-source search made other teams' work visible. "The team next door was working on the same problem" — once that becomes discoverable, information exchange and collaboration follow.
At weekly engineering meetings, "I searched ZEROCK and found this related case" has become a regular contribution — cross-team knowledge sharing has become noticeably more active.
Quantified Results
Faster Problem Resolution
Average time to resolve technical problems fell by 40%. Immediate access to past cases and related information cut time spent on trial and error.
Reduced Duplicate Work
"Solving an already-solved problem" cases dropped by 80%. As searching ZEROCK before starting work became habitual, reinventing the wheel became rare.
Faster New Hire Ramp-Up
Time for new engineers to perform independently dropped from 6 months to 4 months. The ability to ask ZEROCK when unsure reduced dependence on senior colleagues and accelerated self-directed learning.
Voices from the Team
"Before, I'd say I was spending maybe 20% of my day just finding information. Now that's basically zero." (Senior engineer, 30s)
"When we're considering a new technology, I can now quickly find out if someone in the company already knows it well. Even people who haven't met before can connect around shared challenges." (Tech lead, 40s)
"The psychological barrier to asking questions went way down. If I'm asking AI, there's no embarrassment in asking the same thing multiple times." (Junior engineer, 20s)
Looking Ahead
Company B has plans to expand ZEROCK use further. Currently focused on technical documentation, the goal is to bring in project management information and customer interaction history — building a more comprehensive knowledge foundation.
The team is also planning to apply the AI slide generation feature to improve proposal creation efficiency.
Conclusion: Tools Can Change Culture
Company B's case demonstrates that the right tool can change organizational culture. Having a mechanism for information sharing generates the behavior of sharing, which becomes embedded as culture.
At TIMEWELL, we're supporting this kind of information-sharing culture transformation at many organizations through ZEROCK. The same change that happened at Company B is within reach for your organization.
The next article examines document management in the generative AI era — what the internal wiki should look like going forward.