Skip to main content

Startups: Please Disrupt the Public Sector

Startups have successfully disrupted many well entrenched business models, from the automobile industry to the food we eat and what we wear.  So far, startups have had much less of an impact on government.

When will startups focus their efforts on changing the way government agencies serve the public?

Many processes are ripe for disruption:
  1. Government procurement is costly, slow, and inefficient.  Many of the processes designed to enhance competition and provide business opportunities to small companies have produced the opposite of the desired result, creating barriers to competition, rewarding unscrupulous contractors and saddling agencies with failed products and projects. 
  2. Customer service and customer satisfaction have improved in many industries but not so much in government services. Wouldn't new approaches to customer service reduce cost along with better citizen satisfaction?
  3. New channels for customer service.  In a related point, while some government agencies are embracing social media, many have a long way to go.  Do government agencies need their own official social networks?
  4. Mobile apps.  I use mobile apps for parking and also for some museum exhibits, but there is much potential for new apps.
  5. Grants. Government grants are an increasingly important mechanism to fund programs, but grant application and reporting processes are largely manual.  Improved tracking can enhance accountability, and deep learning could tie results to expenditures and lead to more efficient spending.  
I'm sure that many initiatives are underway that are not visible to me, but if there is a sector ripe for change, it is in the public sector. 


Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ by James Townsend Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do