Link: Without a formal mandate

“In almost every case there are stakeholders who are moved by quantitative data (say the percentage of phone calls that could be avoided.) There are also other stakeholders who connect with qualitative human stories. The magic really happens when you offer both types of evidence. Telling the stories, and backing them up with data points for the cost or the impact of what is happening to people, this is evidence with impact. When you make it real for everyone, you can more effectively catalyze change.”

Also, a sort of case study of improving design in state government.
Original source: Without a formal mandate

Link: Without a formal mandate

“In almost every case there are stakeholders who are moved by quantitative data (say the percentage of phone calls that could be avoided.) There are also other stakeholders who connect with qualitative human stories. The magic really happens when you offer both types of evidence. Telling the stories, and backing them up with data points for the cost or the impact of what is happening to people, this is evidence with impact. When you make it real for everyone, you can more effectively catalyze change.”

Also, a sort of case study of improving design in state government.
Original source: Without a formal mandate

Link: Configuring your release pipelines for safe deployments

“Also, it is recommended to not deploy to all production environments in one go, exposing all the customers to the changes. A gradual rollout that exposes the changes to customers over a period, thereby implicitly validating the changes in production with a smaller set of customers at a time… As an example, for an application is deployed in 12 regions with US regions (4) having a high load, European regions (4) having a medium load and Asian regions (4) having a relatively lighter load, following would be the order of rollout.”
Original source: Configuring your release pipelines for safe deployments

Link: Configuring your release pipelines for safe deployments

“Also, it is recommended to not deploy to all production environments in one go, exposing all the customers to the changes. A gradual rollout that exposes the changes to customers over a period, thereby implicitly validating the changes in production with a smaller set of customers at a time… As an example, for an application is deployed in 12 regions with US regions (4) having a high load, European regions (4) having a medium load and Asian regions (4) having a relatively lighter load, following would be the order of rollout.”
Original source: Configuring your release pipelines for safe deployments

Link: Farmers Insurance Tests AI, Automation’s Potential For Speeding Up Claims Process

“AI-powered image recognition couldhelp speed up the claims process for damages related to, for example, windshields. Windshield claims are common and easy to resolve but still often require claims adjusters to go out in the field and make assessments, Mr. Guerra said.”
Original source: Farmers Insurance Tests AI, Automation’s Potential For Speeding Up Claims Process