Email a colleague    

June 2012

Stay Focused, Coordinate and Keep it Simple: Applying Steve Jobs‘ Leadership Tenets to Telecoms and Business Assurance

Stay Focused, Coordinate and Keep it Simple: Applying Steve Jobs‘ Leadership Tenets to Telecoms and Business Assurance

Most everybody who’s read Walter Isaacson’s biography on Steve Jobs enjoyed it.

The book reveals the many facets of this complex man.  You hear about his creative genius as well as his temper tantrums.  All in all, Isaacson did a splendid job of researching Jobs‘ legacy and interviewing close to 100 people who interacted with Jobs across his business life.

Ed Shanahan reached out to me after seeing the industry map I published showing the interplay of assurance and B/OSS functions.  And no sooner did we get on the phone together but the subject of Isaacson’s book came up.  Ed had just finished the book, loved it, and saw important parallels between Jobs‘ struggles and those faced by telecom service providers.

In the early to mid 2000s, Ed was probably the most visible revenue assurance consultant in the U.S.  Not only did he head up the RA practice at TMNG, for several years he also teamed with Telestrategies to deliver seminars at their annual RA conference.

Ed Shanahan is certainly one of the sharpest consulting minds I’ve come across.  And yet, if you put him in a room with 30 random people, you’d probably not pick Ed to be the consultant in the group because Ed’s a soft-spoken and cerebral guy with the relaxed manner of, say, a senior engineer.  And perhaps that’s his secret — an ability to calmly analyze the structure of a telecom’s operations much like an engineer tests the cable stresses of a suspension bridge.

In our interview, Steve Jobs‘ leadership tenets are merely a springboard for Ed’s deeper diagnosis of organizational flaws and how executives and business assurance pros can get things moving in a simpler, better coordinated, and more focused direction.

Dan Baker: Ed, be perfectly honest with me.  What did you think the telecom analytics map of mine you saw?

Ed Shanahan: Dan, I think you did a good job of getting a lot of these functions on a single map and alluding to the many different terms people use whether you call it revenue assurance, business optimization, cost management, etc.

Trouble is, you can‘t look at all those functions and say, “Let’s focus on cost assurance today and revenue assurance tomorrow.”

The best way to run a company, I think, is to start with something simple and understand what you’re really trying to accomplish.  You choose a relatively small number of objectives and then really knock those things out of the ballpark.

And that’s where Steve Jobs comes in.  Jobs‘ view was that design and function are tightly integrated and you need to do things holistically.  And unfortunately, the way most business people solve problems is in piece parts fashion.


Jobs‘ overriding management style was a top down, simple is better approach.  It extended to many minor details.  For example, most Apple products don’t have an on/off button because Jobs considered that rather inelegant.  Then, when Apple first came up with a CD drive for the Mac, he forced the CD drive makers to redesign their drives so there was no sliding tray.  Rather you simply slip the CD into a slot on the side of the machine.  He brought that same sense of simplicity to all Apple products.

Organization Focus

The second thing that Jobs did -- and as he matured as a leader he got better at it — was to adhere to a relatively small number of high-priority items.

Rather than try to do everything, he rigidly focused on what was in the best interest of the company.  And if that meant shedding products or shuttering ineffective plants, so be it.


Another virtue of his was patience.  Just before a product was launched, if he saw that something needed to be changed significantly, he would delay the launch so he could be sure to get it right.

Take the Apple stores.  Just about every retail industry expert thought the plan for Apple stores was a big mistake.  They said, “Apple doesn‘t have enough products to fill those stores”, and they thought it was foolish to put the stores in high-traffic/high-cost areas as opposed to a big box store that you open up in lower-cost suburbs.

But Jobs‘ vision was that the way to make money was to get traffic going by and get people excited about Apple products.  Yet only a month before they launched the stores, they realized something in the design was wrong.  So they delayed the launch by three or four months.

Now as a public company, that was hard for Apple to do, because the company might take a financial hit for a quarter or two.  But in Jobs‘ view, letting the finance guys drive the business was totally upside down.  He believed if you created innovative and elegant products that solved problems, and then priced them correctly -- even at a premium -- you could take a company much further than focusing on quarter-to-quarter economic results.

And you can hardly argue with his results.  Today, Apple has the highest sales per square foot of any US retailer and the highest market cap of any company in the world.

So how can telecoms simplify their businesses?

In our industry, I think the approach that gets it most right is the one that looks at the business as a horizontal flow of activities and data.  That approach forces you to have a cohesive look at running particular business processes and services end-to-end.

And to make that work implies some simplification or rationalizing of what it is that you do as a business.  You need to provide more products that the customer perceives as being high value.  And you remove products and services that the customer sees as low value — or alternatively that are too costly to manage.  Along the way you need to keep your eye on your own economics.  If you do those things well, you are going to dramatically improve the value proposition for your customers and your company’s profitability.

So looking back at what Jobs did really reinforces the need to drive towards simplicity.

Can you give me an example of what you mean by business simplicity?

Well, just the other day I wanted to send Vanguard [an investment bank] a check, but I couldn‘t find anywhere on their website instructions as to how to send them a check.  It sounds kind of silly.  And Vanguard actually is a pretty good company, but the point is I had to call them.

Their statements used to have a coupon that you could tear off and send in with your payment.  But when they redesigned their statements, they got rid of the coupon.  What they are probably trying to do is to eliminate the processing of checks by encouraging people to wire in their money.  That’s fine, but in my case they incurred an extra expense since I had to make a phone call to get information that could have been readily available on their website.

One way or another you need to have a way to pay by check.  A company could charge for the privilege of sending a check, if they felt that was appropriate, but should make it easy and pain-free for their customers‘ to send them money.

OK, so it’s moving towards simplicity and driving a limited number of objectives from a thorough, end-to-end view.  It’s a great strategy.  But how to drive it through an organization given the constraints of corporate politics and people being stuck doing things the same old way they’ve done year after year?

You’re right.  Inserting the strategy into the organization is the biggest challenge.

I’ve found that people react in an organization -- and even in life — by following two guiding tenets.  First, they tend to do what is in their habit or individual nature, and second, they tend to do what is in their best interest — or at least the perception of their best interest.

Now to avoid problems of the first order, you need to be careful about hiring people who are inclined to do the right things.  And if you go back to Jobs, he was a big believer in hiring A-Team players.  He believed A-Team players wanted to work with A-Team players and if someone didn‘t measure up to that potential, then he moved them out of the company.

But assuming you have hired smart and conscientious people, a lot of good management then comes down to the first tenet — getting people to following their self-interest and making sure that coincides with the goals of the larger organization.

This is why I feel telecoms need to pay a lot more attention to their method of compensating people.  This is crucial in sales type organizations or even when rewarding executives.

When you look at how people are typically comped, it generally doesn‘t follow that horizontal flow I mentioned before — say, following an order from beginning to end or following a process to ensure it succeeds.  Usually people are comped on individual slices of that end-to-end process.  One guy is comped on saving costs and another is comped on revenue.  Or alternatively, people in different parts of the world are comped differently.

What’s wrong with having different methods of compensation?  What’s the virtue of having people on the same comp plan?

Actually, the point is not to have people on the exact same comp plan as much as it is to ensure that all comp plans align with what is in the best interests of the company.

Without this alignment, smart people typically do work at odds with what is in the best interest of the company, as they are incented in ways that do not align with the corporate self-interest.

So if you hire smart and motivated people and you build the comp plan to incent people to act in fulfillment of the larger mission, problems start solving themselves and people start working on the right things and dropping the things that are not so important.  It is actually pretty simple, once you take the politics out of the equation and focus on the underlying incentives.

At one US carrier I’m pretty familiar with, the management is focused on two mandates: 1) integrating functions with a new European based parent organization and 2) converting its internal ERP systems to the ERP systems used by (and built by) the new parent company

Now those two corporate mandates make strategic sense, but not if there is not sufficient bandwidth to accomplish both these mandates and to also do the things the company needs to do to remain competitive.  So mandates being what they are, the child company is focusing on them and all other initiatives including new product development, customer support, and high value stabilization and cost management initiatives are taking a back seat.  Net-net the company will lose a year fulfilling corporate mandates and worse will continue to leave profits on the table by deferring high value, non-controversial initiatives until 2 years later.

Ed, I’m curious to hear an example of how current compensation plans cause problems.  What do you propose as an alternative?  And what about the back office?  Do we need to include those folks in the compensation plan too?

The current ways people are compensated in the back office are fine.  Where compensation really matters is in sales, and cost of sales, particularly to B2B accounts.  And here, there are two different views of the world.  One is to incent sales on revenue and assume that other business issues will take care of themselves.  The other approach is to incent people on, for example, gross margin — the direct revenue that you get from the customer minus the direct cost of servicing that revenue.  And that would include things like termination charges and any special places where you might have to have dedicated staff just to support it.

If global sales people are incented on revenue rather than gross margin, then the salesperson in, say, the U.S. is only thinking about the revenue of traffic that originates in the U.S. and vice versa for the guy in Asia Pac.  Each will fight for initiatives that favor his or her commission stream, with no one concerned with the end-to-end profitability of these initiatives.  So the salespeople will make money but the resulting deals may not cover the costs.  And the typical company reaction, once this is understood, is to implement a finance group, with generally either too much or too little power is to act as a fiduciary traffic cop.  In my experience this type of approach is costly, ineffective and leads to organization friction and in-fighting.

The beauty of gross margin compensation is that salespeople begin to focus on end to end profitability by weighing both inbound and outbound costs and revenue associated with the traffic.  So in the prior example, the US and Asia Pac sales persons actually begin to work together to maximize gross margin between their regions, without the fiduciary traffic cop.  They begin to ask questions such as “Why are we terminating this way?‘ and ”What are the alternatives?“ The end result is that the salesperson becomes another squeaky wheel pushing the company in the right direction.

You don‘t even have to issue a corporate mandate because people will start figuring things out for themselves.

How do people in business assurance roles play into this plan?  What’s the impact for them?

It’s a very positive one for them.  People in business assurance know what they are doing.  The problem is they often do not have the appropriate sponsorship or their programs are viewed as a low priority.  If you talk to most people in the field, many of them are frustrated that they can‘t get executives moving on their ideas.

And this is another area where the right incentives will drive behavior that is in the best interest of the company.  If a sales guy comes along and complains that his gross margin is terrible, I, as a revenue assurance guy, can help them evaluate what we can do to improve it.  You can say, “I’ve got three things we’ve been trying to do that will pump the gross margin up another 10 to 15 points.” So the adversarial relationship is replaced with a collaborative relationship and gaps in “rules” and processes are closed with minimal pain as the corporate infighting has been removed from the equation.

Now if the salesperson is incented on gross margin, he’ll go to bat for your program and weigh in on your behalf to his boss, who is incented on gross margin at this point.

Running an assurance shop is really about internal sales.  One of the biggest challenges in corporate life is to sell your ideas and your initiatives.  In every company I’ve been associated with, there are lots of problems and people are jockeying to get funding for their particular programs.

So in an organization where you introduce compensation plans based on the gross margins of horizontal business flows, distractions caused by corporate politics, low value initiatives and “noise” tend to get diminished or eliminated.  You start changing the culture of an organization.

And this is a great way to drive initiatives that will impact the bottom line and support the revenue, cost, or fraud assurance person to get his or her job done.

Ed, thanks for these great insights.  I wonder if we can close by circling back to Steve Jobs.  If we could miraculously resurrect the guy and put him in charge of a service provider, what changes do you think he would make?

When you consider his work designing the perfect mobile phone, Jobs was one of the most innovative telecom executives the industry has ever seen.

Everybody was bitching about how hard it was to use their phone.  Phones had all sorts of features but most people didn‘t know how to use them.  It was a very complicated solution to a fairly straightforward problem which is, “I need a communication device”.

Isaacson on Steve Jobs

I think Jobs would started by driving his whole simplification philosophy.  It wouldn‘t be easy.  Jobs was a relentless manager.  He could be a real jerk and he demanded perfection or at least a very high level of performance.

But the flipside of his domineering personality was that Apple didn‘t get distracted.  He effectively killed the typical fiefdoms that grow up when an organization lacks a strong leader who gives crisp marching orders.

I think Jobs would have also made people at a telecom organization reassess the kind of services they provide right now, and be less attached to the services that were winners two years back.

It shouldn‘t be that complex to provision a service.  Are we trying to do something that is overly complicated?  Are we trying to solve the problem in a way that doesn’t need to get solved?  I think those kinds of questions would bubble up.

Finally, I think the comp plan question would get solved very quickly and he would push for something like a gross margin, something simple to put out, and simple enough for the people getting those incentives to take action on their own initiative.

Copyright 2012 Black Swan Telecom Journal

Ed Shanahan

Ed Shanahan

Ed Shanahan has more than 25 years of global experience in telecoms working with service providers, investors and technology firms.  He most recently served as AVP, Carrier Operations for Sybase 365 where he was responsible for sales operations and service delivery for the company’s global carrier business.  Prior to Sybase 365, Ed was the Managing Partner of Excelerate Partners, a business process optimizations consultancy serving the banking and telecom.  Ed is also a former Vice President and Principal at the TMNG, a consultancy where he launched, grew and managed the company’s Revenue Assurance Practice.   Contact Ed via

Black Swan Solution Guides & Papers

cSwans of a Feather

Related Articles

  • Black Swan Guide: Araxxe’s Revenue Assurance Consulting, Testing, and High Definition Billing Analysis Service by Dan Baker — How Araxxe’s end-to-end revenue assurance complements switch-to-bill RA  through telescope RA (external and partner data) and microscope RA (high-definition analysis of complex services like bundling and digital services).
  • Subex’s IDcentral Monetizes Telco & Enterprise Data to Deliver Digital ID & Risk Metric Services for Financing, KYC & More interview with Shankar Roddam — A new digital intelligence service that monetizes the idle data of telecoms and enterprises while also earning a good return for the owner of the data.
  • Opportunities & Obstacles: Consultant Luke Taylor Muses on the State of the Telecom Risk Assurance Business interview with Luke Taylor — A rambling discussion on the state of the risk assurance business with Luke Taylor, independent consultant in telecom revenue/fraud assurance and solution requirements and marketing.
  • LATRO’s Tips for Launching a Successful Revenue & Fraud Assurance Program for Mobile Money Operations in Developing Countries interview with Don Reinhart — A company building mobile money RA/FM tools and  managed services gives a concise, but detailed tutorial on how the Mobile Money Ecosystem works.  Revenue assurance pros will get tips on  what to look for in analytics/assurance tools, controls, and professional services.
  • A WeDo Conference Talk: Consulting & Analytics: Improving your Business Today, Enhancing it Tomorrow interview with Carla Cardoso & Bernado Lucas & Thomas Steagall — Leading risk management consultants explain their mission and walk-through RA, subscription fraud, and collections cases.  They also explain how analytics and machine learning can supplement process optimization.
  • PrologMobile’s Simple and Brilliant Plan to Save US MNOs Billions a Year in Recovered Phones & Retained Customers interview with Seth Heine — An expert in the mobile phone reverse supply chain explains how MNOs — via a neutral third party information exchange — can recover their original phones on the used market and save huge sums in multi-year customer retention.
  • WeDo Explores the IoT Ecosystem in Search of Tomorrow’s Pivotal Fraud & Business Assurance Solutions interview with Carlos Marques — A veteran product manager scans the IoT terrain, discusses key fraud and assurance challenges, and explains the preparatory steps WeDo is taking to become a key player in this emerging market.
  • New Report: Telecom Fraud & Business Assurance Solutions, Services & Strategies by Dan Baker & Luke Taylor & Colin Yates — TRI publishes a new market research report, Telecom Fraud & Business Assurance Solutions, Services & Strategies.  Free executive summary available.
  • Subex Juggles a Wide Variety of Business Assurance and Big Data Analytics Use Cases interview with Rohit Maheshwari — A expert in business assurance solutions explains top use cases such as: IoT security, big data analytics/AI, network asset optimization, multi-player gaming assurance, onboarding mobile subs, and AI customer analytics.
  • MTN Agility: Mastering Exponential Technologies in Revenue/Fraud Assurance and Beyond interview with Danie Maritz & Tony Sani & Luke Taylor — An in-depth look at RAFM operations and innovation at the MTN Group.  Topics discussed include RA/fraud control challenges, strategies, and MTN’s journey to exploit exponential tech (AI, robotics, and ML) in its RAFM program and support of internal non-telco businesses.
  • From Byzantine Software Contracts to Simple & Flexible RA Managed Services interview with Philippe Orsini — Is the way B2B/enterprise software is sold and delivered today progressive — or is it Byzantine in the age of cloud?  An expert lays out the case for managed services in RA and billing verification.
  • Premiere Experts Set to Speak at Summer RAG Conference in London, July 7th and 8th by Dan Baker — The Risk and Assurance Group (RAG) has announced that its 2016 summer conference will expand into a two-day event and feature many premiere experts. 
  • WeDo Hosts Revenue Assurance & Fraud Management Conference in Washington DC by Dan Baker — Black Swan is pleased to announce what looks to be a first class revenue assurance and fraud management conference being put on by WeDo Technologies, on October 1st and 2nd in beautiful Washington DC.
  • Test Call Generators: An Essential Test & Debugging Tool in Mobile Billing Assurance interview with Steffen Öftring — An “active” test call generator (TCG) can see problems that a “passive” revenue assurance system is blind to.  Here’s a discussion on the test call RA  process, over-the-air calls versus core call injection, and test call networks in global roaming RA.
  • The Revenue Assurance Game: How the Rules Change in the Era of IoT & Mobile Broadband interview with Rene Felber & Gadi Solotorevsky — Revenue assurance is perhaps the hardest of telecom functions to define because the term is used in so many different senses.  This discussion on the evolving role of revenue assurance was catalyzed by a survey of experts in the profession.
  • Day in the Life of a Revenue Assurance Analyst interview with Michael Lazarou — Revenue assurance is much more than a software category.  It’s individual analysts struggling to help their larger organizations get a handle on system errors and coordination problems.  In this interview, an analyst reveals the many challenges of getting the revenue assurance job done at a small GSM operator in Europe.
  • Revenue Assurance: History and New Beginnings in RA Maturity interview with Daniela Giacomantonio & Gadi Solotorevsky — The Roman Forum was the center of commercial life in ancient Rome.  Now, two millennia later, the Forum lives on in the exchange of ideas across countless professions and  media.  In this interview, two Revenue Assurance experts discuss both the new RA Maturity initiative of the TM Forum and the value of telco/solution vendor collaboration.
  • Migrating systems or launching LTE next year?  Don‘t forget transformation assurance & optimisation by Efrat Nissimov — System transformations and network migrations are major  revenue impacting events and they should raise a big red flag.  Why?  Because data integrity issues are bound to crop up as CSPs move vital data from a legacy system to something new.  It’s time for transformation assurance.
  • How can Cable/DSL Internet Providers Meet the Usage-Based Billing Mandate? interview with Ryan Guthrie — The popularity of YouTube, Netflix, and Hulu other video outlets has turned the tables on service profitability for cable/DSL service providers.  Many are moving to usage-based billing, but that largely unprepared for the revenue assurance aspects of this move.  This interview explains the technical challenge and points to solutions in billing, speed caps, and traffic revenue monitoring.
  • CABS Revenue Assurance: How Rural LECs can Recover $284 Million in Revenue Shortfalls interview with Kelly Cannon & Darrell Merschak — Independent rural LECs in the U.S. still rely on the AMA/EMI billing formats for CABS billing, even as that format has proven to be highly inaccurate as a source of inter-carrier records.  This interview includes an analysis and discussion of revenue recovery techniques ILECs can use by leveraging SS7 probes.  Also discussed are billing strategies, traffic dumping threats, and the possible fallout from the FCC’s bill-and-keep mandate.
  • Make Business Assurance Progress Every Day: How to Set Goals, Automate, and Energize Your Team interview with Kathleen Romano — Business assurance (BA) skills have wide applicability outside the revenue assurance and fraud mangement domains.  In this article, a telecom executive explains how she’s applying her BA skills in the Payments area.  In addition to discussing the key operational challenges in Payments, the interview also provides keen insights on setting goals in business assurance, leading a team, and making critical decisions.
  • LTE Rollout: Make it a Smashing Success with Risk Assessment, Controls, and Marketing Offer Analytics by Gadi Solotorevsky — LTE brings splendid new capabilities to mobile users.  But like 2G and 3G deployments before, operators can only make money if they successfuly plan, coordinate, deploy fast, and pay attention to pricing plans and the customer experience.  This article lays out a 3-phase tactical guide on  how revenue analytics professionals can add value in LTE service risk assessment, controls, and marketing offer analytics.
  • RA Prevention: How to Manage Revenue Risks and Communicate RA’s Value to Senior Execs by Shaul Moav — The era of revenue assurance prevention and risk assessment is here.  Several of the mature operators of the world have developed their own methodologies and tools.  Using firefighting and fire prevention as a metaphor, the article details a new commercial software approach explaining the goals, method of risk evaluation, and senior executive dashboards developed for the process.
  • Precision Clockworks: How Revenue Assurance Synchronizes with the Business at Swisscom interview with Marco Pollinger — An expert revenue assurance department is one whose work dovetails well with the lines of businesses it supports.  In this interview you’ll learn how Swisscom manages its revenue assurance function for maximum effect.  The article discusses: the operator’s innovative RA organization, the screening and RA approval of new services, its pre-production bill audits, and its coordination with corporate risk management.
  • Versatile, Portable & Corrections-Savvy: Quest for the Swiss Army Knife of Revenue Assurance Software by Mark Yelland — Revenue assurance maturity models are not cast in stone.  Since  best practices will change over time, it’s healthy to explore moving maturity models forward.  For example, great gains have been made in leakage detection, but RA corrections has been harder to master.  The author dreams about seven functions that should ideally come together in a single all-purpose revenue assurance software tool.
  • Bringing Strategic Planning & Value Engineering to Revenue Assurance interview with Maged Fawzy — Engineering and architectural techniques have a role in revenue assurance.  This interview with a top Egyptian RA consultant explains how continuous risk assessment and long range — yet flexible — RA planning can sharpen a carrier’s RA program and lead to better use of revenue assurance software and integration services.
  • Forensic Fossils: Is Your Revenue Assurance Shop Fit for Display at a Natural History Museum? interview with Jim Marsh — Without the continuous guiding light of seasoned revenue assurance leaders, even the best teams of RA professionals, technology, and business processes can fossilize and lose their vitality.
  • Revenue Assurance: The Magical Market Cap Multiplier by Van Howard & Curtis Mills — Many operators today consider revenue assurance yesterday’s opportunity.  But this article shows why significant revenue and cost leakage can still go undetected, even in companies with dedicated RA departments.  Also discussed are the benefits of a broader or more “forensic” approach to revenue assurance, an approach that boosts the bottom line regardless of the automated tools already in place.
  • From Risk to Robust: Turning the Big Picture Into a Real Agenda for Change in Telecoms by Eric Priezkalns — Inspired by a Financial Times article written by Nassim Taleb, author of “The Black Swan”, here is an insightful and entertaining primer on telecom risk management.  The article takes ten risk management lessons from Taleb and applies them specifically to the communications industry.  You’ll learn about the value of small scale trials, organization accountability, cures for a blame culture, incentives that work, the power of simplicity, and more.
  • Synthesizing the Telecom Business Assurance Practice With the Analytics World by Dan Baker — Business assurance is a wrapper term that allows you to draw a circle around various telecom assurance, control, and optimization activities.  This article maps business assurance as a subset of telecom analytics, constrasting it with marketing analytics while a diagram shows where biz assurance fits in the larger B/OSS world.
  • CABS Revenue Assurance Disputes: May the Carrier With the Best Data Win by Cheryl Smith Rardin & David West — Revenue assurance innovation is far easier when partners cooperate to make it happen.  This articles shows how a U.S. operator, software vendor, and consultant teamed to develop a breakthrough in Carrier Access Billing (CABS) assurance.  Learn about: the dispute resolution data gap that needed to be filled, the partnering strategy, the implementation challenges, and payback results.
  • Revenue Assurance vs.  Business Assurance: Who’s the Rightful King of Controls Software? interview with Sergio Luis Silvestre — Business controls software, originally developed for RA, is finding application in other areas of the business such as internal audit, collections, security and risk management.  This article argues that “business assurance” is the best term to describe this broader set of  controls software that can find a home in numerous departments or functions of a CSP’s business.
  • PwC on the Business of Revenue Assurance Consulting & Mentoring interview with Tim Banks & Dan Stevens — Revenue assurance consulting firms offer a broad range of services to clients these days.  The article explains the practice of mentoring RA mangers and providing a CFO with visibility on the status of an operator’s business controls.  Perspective is also offered on the value of RA software and the opportunity to broaden the RA practice scope.
  • Robots for Hire: Verifying Accuracy In the Age of Complex Mobile Billing/Charging interview with Xavier Lesage — As real-time charging and complex lifestyle calling plans gain credence across the globe in wireless, billing quality issues will rise in importance.  This article discusses a unique managed services approach to invoice testing and roaming fraud protection that checks results against advertised or published source data for the utmost accuracy.
  • Ericsson: Revenue Assurance Consulting With an NGN Flavor interview with Thomas Steagall — Helping operators detect billing and provisioning problem is merely table stakes in the RA services business these days.  The article discuss why operators need to ramp up their RA function with service experience and group-wide financial health monitoring.  Advise is also offered on: key RA maturity questions, risk-and-reward contracts, and how to extract greater value from software investments.
  • Do-It-Yourself RA for Small Operators and MVNOs interview with Mark Yelland — Budget-minded small operators and MVNOs are no longer hamstrung in RA capability anymore.  This article offers high-leverage strategies for operators who cannot afford expensive RA software tools.  With  data access, brains, and a DIY philosophy, any small operator can map a  path to greater RA savings, maturity, and program growth.
  • Revenue Assurance Maturity: Report From the Arena interview with Eric Nelson — Revenue assurance maturity can‘t be easily computed.  How do you  compare the KPIs of Comcast billing with that of mobile money RA in Western Africa?  Even still, this article offers some universal RA wisdom from a straight-shooting veteran of carriers large and small.  Topics discussed include: dashboard or process, COTS vs. inhouse solutions, and tips on gaining internal support for the RA practice.