I strongly recommend Steve to any organization seeking strategic telecommunications planning and a reduction in telecommunications operating costs.
Len Ludwig, President
First Portland Leasing Corporation
A Strategic Telecommunications Planning (STP) project leverages telecommunications to satisfy both internal operating requirements and a client's business or strategic objectives.
Teleconvergence applies our marketing as well as our technical expertise to meet those needs. STP applies when a client’s business requirements become as or more important than the client’s telecommunications or other operating needs. .
For example, while selecting a backup power source for a system is part of standard telecommunications consulting, working with a client to establish contingency plans to ensure telecom-related business operational continuity in the face of unforeseen events and natural and/or other disasters (See the first article below) creates the need for STP.
Other examples of Strategic Telecommunications Planning are:
Your persevering desire to satisfy our unique requirements, and your never-ending attention to detail has contributed to making me a well-pleased customer of Teleconvergence. Because of your enduring efforts, the public safety needs of Tillamook County will be satisfied for some years to come.
Mark Schackart, Administrator
Tillamook County Emergency Communications District [911]
IT is traditionally responsible for preparing for contingencies or emergencies involving power, networks, file backup, physical access to facilities, etc. Teleconvergence’s Contingency Telecommunications Planning is different in two aspects. First, it addresses not just “normal” or “adverse” conditions, but includes plans for operating under extraordinary circumstances as well. Second, it is pointedly focused on telecommunications continuity, although the form that takes may be dramatically different than day-to-day operations.
Under certain circumstances, clients can also turn such contingency capabilities into revenue generating possibilities, as noted in Turning a Contingency Plan Into a Business Opportunity in the Strategic Telecommunications Marketing (STM) section.
What is the essential nature of an intelligent contingency business continuity plan? Since no one would deliberately create an unintelligent one, any intelligent business continuity plan must have at least two components: a Plan A, which represents normal operations, and a Plan B, which assumes normal operations have been interrupted, if only because NO plan works as planned forever.
Many experienced businesspersons also realize (1) that they can't plan for everything and (2) that they can’t plan for what they haven’t thought of, and so they also create a Plan C solely to maintain critical operations, because whatever affects Plan A might just affect Plan B, too.
Teleconvergence offers two related primary continuity/emergency planning services.
Telecommunications Continuity Planning deals with contingency planning for interruptions in telecommunications services.
Business/Natural Disaster Continuity Planning and Preparedness entails the ability to strategically deploy telecommunications and related technologies to deal with potential as well as unforeseeable and extraordinary emergencies.
Not all disaster and emergency scenarios are the same, although all inevitably prevent the client from operating normally. Simple scenarios involve malfunctions in a client’s system or network. Other scenarios interrupt operations by making the client's premises dangerous or uninhabitable (e.g. gas leak, fire, terrorism). Still others prevent access to the client’s premises (e.g., flooding, ice storm, road closures) so that no one can get to the phones. In either event, what do you do? How to you keep operating?
Teleconvergence's services help clients plan ahead for such contingencies, greatly minimizing possible risk, and certainly costing far less money than it will if they are not anticipated. Not thinking it through beforehand, it seems to us, inevitably puts you at great if not almost unlimited, risk.
Planning like this doesn't take place in a vacuum. It requires awareness of business priorities, operating needs, staffing conditions, budgets, and, of course, technological alternatives, but only if consistent with the foregoing. Technology is not the main consideration, but only a tool to meet business requirements.
If you agree, and you're interested in our aproach, please read the other two articles in this section.
Do these scenarios really apply to your organization, and if so, how ready are you to deal with them? Read the following checklist and make your own determination.
At one time or another, every business owner thinks about what might happen if primary telecommunications facilities were disrupted or become generally unreliable. Many managers who have experienced such events take steps to ensure non-recurrence, such as using backup carriers and networks. Unfortunately, many of these plans turn out to have the same Achilles heel, meaning very little if any additional protection has been obtained.
We've had clients who thought they were adequately protected by having two suppliers. It always makes sense to use multiple suppliers so that if one is performing poorly, traffic can be shifted to another. It's a good, basic Plan B. However, in most buildings, all telecommunications facilities are located in the same area, so if that area is damaged by fire or water, all facilities are equally at risk, and nothing is gained.
Some clients have taken the extra step of running separate feeds from different suppliers into different parts of a building. This affords greater protection, but it's also happened that some distance off, the separate feeds had the same route to the client – and a backhoe pulled up the cable(s) before the feeds diverged – with obviously disastrous results. Did the client need a plan C? Perhaps, but at least having a plan B offers greater safety than a single plan A.
Teleconvergence helps our clients decide what they will do when Plan B also fails, as it inevitably will.
The PSM process uncovers and analyzes existing processes and procedures within the client's environment that, unknown to the client, reflect either (a) workarounds or (b) existing undocumented requirements that are being met outside published work descriptions. PSM can result in increased productivity, reduced operating costs, and increased employee satisfaction.
PSM is Teleconvergence's benign approach to process improvement. It is at the very bottom of the business analysis hierarchy. It does not pretend to re-create the universe nor re-structure the planet, or even to finely floss an organization or a division thereof.
Instead, PSM is, quite frankly, a way to grab low-hanging fruit, to identify miscellaneous tasks that are ripe for technological change or unnecessary functions which can and should be deftly deleted from daily routines and quietly buried, unlamented. Most organizations realize that inefficiencies exist, but they are not willing to radically turn themselves inside out when they suspect that a little spring cleaning will accomplish most of what's needed without creating undue disruption.
Over time, we’ve come to realize that systems client management thought were operating poorly or were being stretched beyond capacity were in fact being underutilized.
They were also underperforming because system users were caught in a quagmire of cumulative workarounds that reflected neither their job descriptions nor the work they were supposed to be doing. Instead, daily work flow required continual and time-consuming sidesteps of catch 22s that had to be overcome to get any real work done at all
PSM uncovers and analyzes existing processes and procedures within the client's environment that, unknown to the client, reflect either (a) workarounds or (b) existing undocumented requirements that are being met outside published work descriptions.
Unless documented, detected and corrected, such activities will be nonproductively perpetuated in future systems, creating still additional tiers of workaround activity to enable the unrecognized work processes to continue. The PSM approach either eliminates this activity or uses technology to integrate and automate it. In either event, the cost reductions and productivity improvements are both predictable and documentable
While some of Teleconvergence's work is strategic, other aspects are simultaneously tactical and practical. PSM is bottom up, focusing on actual needs of individual business users in the context of a potential technological solution. It is natural for us to look for ways to apply technology to help such users achieve their objectives.
It is not as obvious that we also expend effort and time identifying and eliminating tasks and processes that are unnecessary in the first place. Since our intentions align employee objectives with those of the organization, we find very little resistance to exploring avenues of improvement that would simultaneously benefit both.
Business Analysis is part of our basic perspective and approach to project management and system evaluation. Systems don't just do things. They exist to perform processes that lead to the satisfaction of business objectives. We can't articulate your requirements until we understand your business needs, future plans, and operating priorities.
The Teleconvegence Process section explains this in detail, so our services in strategic operations, including PSM, shouldn't come as a surprise. Teleconvergence is admittedly a different kind of firm, and it is the Process that differentiates us.
Since Teleconvergence normally performs PSM along with our other functions, incremental cost is minimized, and we're under no obligation to keep digging and digging until something is discovered. There's far less functional disruption and staff resentment as a result, since if nothing procedurally redundant or superfluous turns up during our fact-finding and interviews, we quickly move on.
Moreover, management will be far more willing to take steps to correct deficiencies when newly-determined procedural efficiencies and insights can be implemented either in conjunction with a new system, or by modifying existing systems and procedures to eliminate unnecessary workarounds.
This is how Teleconvergence can identify unique client needs that, if satisfied, result in optimal system or software selection and how we determine the requirements for the platform upon which much of an organization's future productivity can be predicated.
In most cases, there is neither the corporate will nor a driving need for a major shakeup. PSR makes sense for most organizations because most organizations do not consider themselves either completely broken and in need of re-creation (Reengineering) or even in need of major restructuring (Business Process Review).
Moreover, since the last system change or upgrade resulted in the current layer of workarounds and inefficiencies, the new system will similarly have to be modified to remain consistent with the only way to "get anything done around here". This task is accomplished by employees consuming significant company time without management knowledge, inevitably accompanied by much grumbling also not overheard by management. Without a fresh look, the Law of Diminishing Returns will doubtless reapply, and the desire for a better system will again raise its head.
All of this, naturally, is independent of:
Equally important is that, after a while, the workarounds become indistinguishable (by the workers, at least) from official work procedures designed to get the work done, which leads to "We've always done it this way because that's the way it's supposed to be done," and besides, "it's the only way we know how to do it."
Compounding the issue is the fact that, in today's downsized, experienced-workers-go-first environment, the entire departmental collective history may not be that long. That means, in other words, that no one still working may actually understand what the tasks being performed were originally designed to accomplish.
Teleconvergence first discusses individual job descriptions and departmental/work unit functions with client management. We also try to learn the expectations at various management levels regarding the expected effects of an impending system change.
Then, however, rather than simply accepting management's statements about work parameters and process objectives, we attempt to identify and independently verify:
The next PSM phase is an appraisal of existing (meaning actual, not as formally described) work procedures, including how and by whom and in what order the work is being done.
Teleconvergence then provides management with statements of actual work requirements, documents actual work practices, and makes suggested changes to increase productivity and/or lower cost. We frequently include in our presentation our estimates of how much time is being spent, how much time could be saved, cost savings estimates based upon employees’ burdened hourly costs, etc. Some recommendations inevitably require system change, others may not.
Once management decides among behavioral and process alternatives, Teleconvergence can then evaluate system alternatives with the confidence that the entire effort will be, well, productive.
PSM helps identify who is doing necessary as opposed to unnecessary work, and which work processes can be eliminated and which can be combined. Additionally, PSM helps to identify and highlight the skillsets really needed to satisfy current and future work demands.
Needless to say, savings not only accrue from the reduction in procedural steps and work process time, but also from the potentially lower number of employees required to perform the same work in less time. Such productivity gains from procedural modification and employee cost reduction can far exceed savings derived from productivity resulting from system change alone. In cases where productivity can be increased to the point that fewer employees are required to do the work that is really necessary, the PSM process minimizes subjectivity in any subsequently undertaken staff reductions.
When employing any of these methodologies, layoffs are neither the objective nor the solution. It is not a simple matter of identifying who is doing the work vs. who is doing the workarounds. Parkinson's Law ensures that any time potentially saved by using workarounds has long since been filled with other activities. It is important to remember that each and every workaround was at one time absolutely required --at least once-- or else no one would have gone through the effort of creating it.
Since workaround tasks are incorporated into the overall work process, a person spending 100% of his or her day on workarounds cannot be fired and the tasks left undone without the entire work process collapsing of its own weight. Practitioners perform workarounds indistinguishably from any other tasks, except frequently, the workarounds are regarded as more prized functions because they are either seen as shortcuts or else are absolutely necessary to make everything else run on schedule.
What the presence of significant workarounds does indicate, though, is that at least some necessary work is not being done directly. This means that either (A) needed work is not being done or is being only partially done, or, (B) if all work is being done, then there are more people involved in the process than necessary if not for the presence of the need for workarounds.
Another way to look at it is that the real productivity improvements come not from retaining the workarounders (who are generally the most effective employees), but instead from reworking the processes to take advantage of technology and simultaneously eliminating the need for workarounds in the first place. This creates a requirement for even more efficient workers because the process itself will have become that much more effective.
Employees performing workarounds are characteristically quite flexible and capable of learning new tasks because over time they inevitably have to adapt the workarounds to new systems and procedures. Does that mean that such persons should be retained and others fired? Not necessarily. Only after the nature of the real work to be done is revealed once workaround layers have been shed can the skillsets necessary to do such work be determined.
Is it possible, then, to perform PSM (or other work process analysis) on a department or a function (such as order processing) and realize productivity improvements that eliminate the need for new systems? Yes, it's possible, but so is the counter scenario that the resulting increase in productivity will strain existing systems beyond capacity and thus necessitate system change anyway.
Fortunately, in such a situation, the organizations benefits doubly: first, because the initial phase brought increased productivity and reduced cost without the capital expense of a new system. Secondly, because the greater work output will demonstrate exactly where (and which) new system capabilities are required to sustain the higher levels of work output and productivity. Finally, with the slack removed from the system, it will become obvious where system robustness must be enhanced, where redundancy must be implemented, where excess capacity must be planned, where backup plans must be formulated and tested and initiated, etc.
Similarly, where the new workload requirements are beyond the capability of even the current workforce, the analysis can determine those traits and knowledge sets necessary for future productivity, help the organization recruit employees with newly validated academic or technical qualifications or work-related experience, and help the organization better recruit employees for advancement from within employee ranks based upon specific abilities rather than making do with traditional office skills or work experiences.
In fact, perhaps the definition of PSM should be changed from Procedural Strip Mining to Productivity Success Methodology…
Teleconvergence assists top management and acts as part of a client's management structure. We participate in formalizing objectives and in recommending strategies to meet them. Over time, we learn the personality of a client, the ethics, the way things actually get done within the firm, and we use that perspective to enhance the technological, financial, and competitive positions of our clients in every possible way
Len Ludwig, President
First Portland Corp.
When a client needs not a single project performed, but many of them, or when the client needs help in simultaneously implementing long-term strategic decisions, in reducing cost, and in gaining control over both telecommunications billing and contractual relationships, then a retainer relationship with Teleconvergence may be in order.
The Teleconvergence Telecommunications Retainer -- Not Outsourcing (this article) discusses the differences between traditional outsourcing and our retainer services.
The Teleconvergence Retainer FAQ fully describes the retainer relationship.
Traditional Outsourcing: Firms that typically outsource are huge organizations that have decided that equipping and running their information or communications systems is distracting them from their "core business."
Outsource suppliers are usually equally large organizations, so the process becomes a tango of elephants making financial and strategic tradeoffs and concessions. Giant Outsourcers supply the systems and software and technical staff. Outsourcers assume that all hardware and software will be replaced during the three to five year contract period and so they make money on the equipment and on their service fees and frequently by paying staff less. The client (now regarded as a "strategic partner") negotiates a flat rate or the equivalent and is glad to have someone else shoulder the responsibility.
The Teleconvergence Retainer: Teleconvergence clients are different. They replace telecommunications equipment only when absolutely necessary, and they exert constant vigilance over costs. They regard their information systems as key corporate assets they would never entrust to anyone else. Teleconvergence clients are not usually very large companies, but they are usually heavily communications-intensive and/or they are companies for whom technology or telecom assumes strategic importance.
The Teleconvergence retainer is equally different. Teleconvergence does not supply equipment or software or personnel, nor do we assume responsibility for existing systems or staff. In fact, one of our chief attributes is that we aren't a vendor, and so we can impartially help a client select from among the entire universe of possible suppliers and services, and will even help the client recruit technical staff.
If you're a small-to-medium sized firm that would like to grow the expertise, we can help there, too. Teleconvergence can begin by performing the project work that requires expertise, then later train your staff to perform and administer operations and billing, or whatever combination of the two makes the most sense for you. If your firm is in long-term growth mode, Teleconvergence can also train employees to perform much of the work that has to be done to manage the telecom function on a regular basis, moving us to an review/oversight and strategic role rather than an operating one. Either way, your needs come first, and our objective is to satisfy them.
The actual teleconvergence relationship is treated fully in the next article, The Teleconvergence Retainer FAQ.
If you're a very large company or a good-sized one that is geographically distributed – and you internally lack the telecom resources necessary to grow your company consistent with your business plan, it may indeed make sense for you to outsource your telecom operations to another large corporation, although certainly not your strategic direction nor your oversight capability and prerogatives.
Teleconvergence understands the outsourcing business although we don’t compete for it. A prudent step would be for you to retain Teleconvergence to help you manage the outsourcing selection process by working with you to define your requirements, create the necessary detailed RFP (Request for Proposal), and then assist you in evaluating the responses. Afterward, once the outsource entity has been selected, we can assist you by periodically reviewing outsource entity performance, vendor bills (or outsource entity rebilling) for equipment and usage, and by helping you renegotiate line items or entire agreements, as necessary. One slight variant on the foregoing is that we may be able to help you directly if you simply lack needed telecom oversight in the Pacific Northwest.
As noted earlier, for more information regarding our retainer services, please read The Teleconvergence Retainer FAQ.
1. What Is The Teleconvergence Retainer Service?
It's a longer-term retainer agreement whereby Teleconvergence essentially acts as the telecommunications manager for a client, possibly working to complement IT staff in areas where they lack specific telecom expertise. Your existing staff continues to administer the day-to-day telecom function.
2. What are the telecom functions that in general can and shouldn't be outsourced, even on a retainer basis?
These functions theoretically can be outsourced
These functions shouldn't be outsourced:
3. Which of those functions does Teleconvergence perform?
We perform only the first -- Infrastructure, Systems, and Strategy -- and we help train client staff to properly control the others.
4. What exactly does Teleconvergence do?
On a non-recurring or project basis we work on:
Our recurring functions include:
On a demand or planned proactive schedule we actively monitor:
Finally, we help the client manage internal control and administration over:
5. Do you duplicate the work my clerical staff already does?
Not at all. In fact, we may simplify it, since we know which invoices require constant scrutiny, for example, and which need only be looked at on anniversary dates. Similarly, we work diligently to streamline procedures and automate activities wherever possible.
6. Is the Teleconvergence Retainer very expensive?
We think you'll be pleased to discover how reasonable it is, especially compared to what you'd have to spend for full-time professional staff to do the work. It's a forward-looking process that assumes significant time usually being expended at first, then a leveling out after a while. We try to negotiate flat payments largely independent of monthly workload, similar to how one pays a utility when ignoring seasonal fluctuations.
6. Is there a lot of paperwork to get started?
Generally not, because initial estimations and activities are subject to ongoing mutual review to ensure that the client agrees with our priorities and activities.
7. How do we know that outsourcing is the right strategy? How do we regain control if we think it's not working out?
First of all, outsourcing to Teleconvergence is a financial decision, not a strategic one, So there are no long-term or irreversible implications. Secondly, by outsourcing with Teleconvergence, there's no need to be concerned about regaining control because you never lose control. You're not putting authority into anyone else's hands; by retaining us, you're simply allowing us to share the responsibility with you.
8. How big is our committment? How long do we have to commit? What happens if it doesn't work out?
These are all reasonable questions. You should to only what seems reasonable to you. The initial commitment is generally for three to six months, if we've not done project work for you before. Regardless of the size or the term of the commitment, our retainers are always cancelable on reasonable notice, and all terms and conditions are spelled out in clear English (or Spanish) in our retainer agreements.
9. How do we know if we should begin by outsourcing our telecom function or just begin with a single project?
You should begin at the beginning, with what you need the most. If it's a single project, we'll do that. If it's a few of them, that's OK, too. If you have some projects that must be done, but you're really not prepared to administer the projects or the function, we can set priorities and manage the situation properly.
But we have to start at the beginning, by finding out what you need and determining if and how we can best be of help, no matter what sort of label we pin on it. If that sounds reasonable to you, why not begin by calling us to discuss your situation?
Throughout the 20th century, multiple levels of management were responsible for business processes, business systems, employee productivity, and employee satisfaction. The dot-boom-dot-bust that began the 21st century eliminated entire levels of such management, and effectively transferred the responsibility for all systems and procedures to IT, but not responsibility for employee satisfaction or productivity.
The outcome has generally been more efficient IT system procurement, but also, unsurprisingly, what has been perceived as ineffective IT responsiveness to the needs of office employees. Unfortunately, in many companies, the inability of IT and business unit staffers to understand each other's needs has resulted in both personnel and communications systems that simply fail to communicate.
Business managers traditionally placed great emphasis on producing teamwork among individuals to increase productivity, maximize job satisfaction, and minimize turnover. It's different today. IT views its business role as connecting hardware and systems and managing processes to meet financial and operating objectives. Moreover, IT may simply have no metric in place to measure employee satisfaction or productivity, nor does it have any responsibility for the result.
Moreover, if one asks (as we have many times), "Which department, or more specifically, which executive is responsible today for productivity and employee satisfaction?" the answer in many companies, sadly, is "no one."
Frequently, the greatest mistake companies make when trying to resolve IT's inability to communicate effectively is to make IT responsible for the solution. IT naturally goes about it from IT's point of view, which is something, as business units are not reluctant to point out, they feel is largely responsible for causing the problem in the first place. The results are eminently and inevitably predictable.
While traditional business process analysis (a common IT tool) can alleviate some of the symptoms, it also frequently fails to get to the core of the problem. Remaining and festering issues typically include mutually exclusive vocabularies and widespread and undocumented "workaround" business processes. Equally or even more harmful is the damage that has been done to the always undocumented, delicate, and now unsupported fabric of rich non-dotted line relationships that make great companies successful.
Consider these contrasts:
Which perspective do you think is more likely to be able to articulate business unit needs in terms that IT can understand and respond to and which will best ultimately satisfy all parties concerned?
The problem cannot really be resolved from within IT because IT is unwittingly complicit in perpetuating the problem. In a formal IT-directed dotted-line-relationship-only environment, where the real need to address both personal business requirements and the interpersonal aspects of business relationships remains unsatisfied, what invariably occurs is the creation and perpetuation of workarounds, frustration, and low morale.
Teleconvergence believes that properly created systems and processes create cohesiveness within and among business units by effectively formalizing the importance of non-dotted line relationships among individuals.
If the situation is rooted in or aggravated by poor communication, Teleconvergence may be able to help as an honest broker because of our lack of bias in resolving technologically-related communications problems.
Teleconvergence can determine the true operational, communications, systems, workflow, and interpersonal requirements that exist throughout an organization and turn them into specifications to which IT can respond appropriately by creating appropriate organizational capabilities.
Teleconvergence -- and this must be understood clearly-- in no way replaces IT's technical functionality. Instead, Teleconvergence simply represents the business acumen coupled with technological insight that has been lost due to the departure of so many experienced non-IT business unit managers and staff.
IT thus retains management responsibility for all systems, but the process allows Business Units to express their needs through Teleconvergence by using the business and even interpersonal vocabularies that so often unfortunately have become lost in translation.
Doesn't that sound like the win-win both sides would like to accomplish?