Your enterprise has more data and more data silos today than ever before. But your employees are are struggling to keep up. Even routine tasks are now impeded by information discovery issues: “Where’s that server again?”, “Where’s that report?”, “Where are my new team’s resources?“.
Your vital information assets should not be this difficult to find.
Your employees are working around these problems with yesterday’s solutions…
Teams sometimes create DNS records (like CNAMEs) for their resources under a subdomain they have been given. But this has its shortcomings.
DNS is an incomplete solution. Only some resources like servers can have DNS records.
Enterprise subdomains are unwieldy. You’ll be familiar with horrors like “thing.env.team.example.com”.
DNS is a top-down naming system. It doesn’t allow people to reference things in a way that’s natural to them.
Employees may use in-silo search functions (like wiki search) or an enterprise search appliance to find business records. But enterprise search rarely delivers the promised goods.
In-silo search is primitive. Most in-silo searches give reams of irrelevant results.
Search is not easy. It needs tuning by good specialist search engineers to work well.
Many offerings won’t suit your enterprise. Cross-silo search offerings do exist, but whether it’s the proprietary 3rd party cloud, or the premium price tag, they are rarely suitable for larger enterprises.
When other solutions fail, employees resort to the humble browser bookmark. The problem is, bookmarks only work well on small scales.
Employees cannot share or reuse bookmarks. They can’t use the naming effort of others in their team, so they must reinvent and maintain their own bookmarks.
Switching teams means reinventing your bookmarks. Each team’s information architecture is different, so employees must reinvent their bookmarks each time they switch teams.
Bookmarks are confined to the browser. They aren’t easily available outside it.
Epi connects your employees to your enterprise’s accumulated knowledge, no matter which silo it’s in.
Locate resources without waiting for a flaky enterprise wiki server to wake up. Find that report you’re meant to work on fast, not on the 4th page of search results.
Bringing new employees on to a team is hard, but Epi makes it easier. Just add the new employee to the team’s linkbase, and they can start finding the team’s resources.
An Epi team linkbase accumulates precious contextual knowlege of what a team call its resources, and where they live. Team members can reuse each other’s naming efforts.
Knowledge sharing between different teams in an enterprise is hard, but Epi can help. Want to know where another team’s code repos or CI server are? Look at their linkbase.