Engineering discussions tend to focus on how to improve the KPIs in the sense of network quality, reduce drops, improve accessibility, etc. Fixing coverage holes is always noted, but this tends to be fixing coverage the "right" way, which is typically the long term capital improvement. Long term network fixes come through large scale site build, low-band spectrum acquisition, improved hardware deployment, or alternative network types which is typically large capital expenditures.
Engineering KPIs such as retainability (drops) and accessibility (blocks/coverage) are focused on because they are supposed to mimic the customer experience. Or at least they "were" supposed to mimic the customer experience. As engineering performance in these areas became the measurement of team success, an interesting line of deviation may have occurred. There's long been the hidden philosophy of RF engineers that a customer can't drop a call if they can't make it, that network quality will improve if there's only good coverage, and that if a customer hangs up first it isn't a drop.
RFAssurance is a Telecom Technology Services, Inc department specializing in the support of wireless networks. RFAssurance provides support and consulting for RF RAN and Core Network tools, processes, and results to improve network design, optimization, and general performance. Our managers, engineers and software developers are subject matter experts with various design & optimization tools, database structure, web implementation, and their practical applications. For how we can help support your network, contact us via email at email@example.com