Eden Technologies and the art of finishing the job

The request sounds innocent enough: finish sooner. In Eden Technologies’ account of a global bank workspace upgrade, the business wanted the program accelerated by 25%. There were 19,000 users involved. Hardware was being refreshed alongside the workspace. Other critical systems depended on the deadline. A change to the calendar meant changing the choreography of people, equipment, and support across countries.

A bank asks the clock to hurry

According to Eden’s case study, more than 400 field resources worked across the US, UK, Canada, and Asia. Migration Manager software gave the bank a global view of progress and obstacles. Eden says its modular delivery approach accommodated the acceleration without extra cost. The coordinated refresh avoided nearly $38 million in depreciation and $3 million in third-party support costs.

Those are reported cost avoidances, rather than Eden’s fee. The mechanism is alignment: two related changes, one coordinated program, and enough visibility to adjust the work when the deadline moved. The technology mattered. So did knowing where everybody was supposed to be.

Eden occupies this junction between engineering and organization. Its consulting practice covers strategy, architecture, project planning, merger integration, and training. Its transformation work includes desktop migrations and network integration. These services address a familiar predicament described on its consulting page: the team responsible for keeping today’s systems working must also find time to replace them.

The application nobody counted

Ask what goes wrong early and Eden’s migration advice gives a remarkably unromantic answer. Its consultants identify inaccurate application inventories as a principal cause of overruns and delays. Their 2017 planning guide includes web applications, macros, and plug-ins in the count. An endpoint-management report is a starting point; people in the business still need to check it.

That makes intuitive sense. A computer can report installed software. It takes a person to explain which spreadsheet macro closes the monthly accounts. The inventory becomes a negotiation over what to keep, what to standardize, and who will test it. Eden’s advice calls for executive backing because the project manager needs cooperation from colleagues who do not report to them.

Application packaging makes installations repeatable by specifying settings, locations, and licensing. Eden reports more than 10,000 applications packaged. Its service includes compatibility work, virtualization, acceptance testing, and training technical staff. The volume is interesting because it suggests repeated encounters with the awkward exceptions that a clean project plan tends to conceal.

The price of touching a machine

Sweeney’s 2016 budgeting guide separates four questions: how many machines, how much hands-on upgrade time, how many applications, and what training is required. The distinction between billable human time and unattended loading time is particularly useful. A progress bar can run for an hour without consuming an hour of an engineer’s attention.

Eden’s historical guidance describes fixed-fee packaging per application. But automation has preparation costs. Its planning advice allows manual installation when only a few people need an application and packaging would cost more. That is a useful purchasing rule: calculate whether repetition repays the setup work. A beautifully automated process can still be an unnecessarily expensive one.

Implementation also depends on decisions software cannot make. An application owner must participate in testing. Leaders must settle competing preferences. Pilots must exercise communications and logistics as well as the technical build. Eden’s second planning installment warns that a poor first experience can make users seek later migration slots, disrupting the schedule. The early failure can be confidence.

A service business with a software habit

Eden sells several ways of getting work done: a consulting engagement, an outsourced work stream, extra development capacity, technicians for a rollout, or recruits for a client’s own team. Its software practice covers mobile applications, cloud-enabled applications, and legacy re-platforming. Managed services can take responsibility for an entire function or selected tasks.

The distinction lies in combining those capabilities with migration tools. EMMA, documented in 2017 and a 2018 industry feature, joined analytics, automation, and project management for technology moves. Eden also describes BirdsEye for inventory reporting. Its partner roster includes Microsoft, Citrix, Cisco, and ReadyWorks, while the company describes its approach as vendor agnostic.

For buyers, the relevant comparison is with assembling the same capabilities internally or across several specialist suppliers. Eden’s proposition is coordination across the pieces. That matters when offices are scattered, engineers are scarce, and several systems must change together.

The customer stories give that proposition texture. At Weil, Gotshal & Manges, Eden reports training, migrating, and supporting more than 3,000 users in 10 countries. For the New York Stock Exchange, it describes modular Day-1 and Day 1-100 data-center integration programs that carried lessons between acquisitions. The common product is a repeatable way to manage a complicated change.

The field-services offering makes the physical side explicit: engineers and technicians need sourcing, onboarding, training, and management. Eden describes a vetted international network of partners and vendors, supported by program and logistics management. Its staffing practice also offers permanent hires and project resources. A buyer can therefore ask whether the missing ingredient is a temporary deployment team, a specialist skill, or ownership of a whole work stream.

The guides belong to the Windows 10 era, and their implementation details belong to that era too. Their organizational questions travel better: what exists, who uses it, who approves the change, and who supports it afterward? A checklist earns its keep when it forces those answers into the open before a date becomes a promise.

The cardboard-box test

Eden’s completion philosophy supplies the most memorable detail. A project is finished when the solution works, users and engineers are trained, documentation is complete, and the equipment’s cardboard boxes have been thrown away. The company calls this “Done. Done.” It is a small phrase with a rather demanding receipt attached.

“Actually, that last 2% is the most important part of service delivery.”Eden Technologies, Our Philosophy

Its published method moves from defining success through planning, development, testing, piloting, deployment, enablement, and maintenance. Communication runs throughout. Readers can borrow that sequence, but the sharper lesson is to agree on completion before starting. Someone must own the tests, someone must own adoption, and someone must own what happens afterward. Otherwise, the boxes remain.