Inside the building where government workers and contractors were watching the health care site melt down, Mr. Dickerson was shocked: The government had none of the modern tools to track, second by second, visitors to the website. And it had no way to figure out why the site was crashing.

Mr. Dickerson, who was part of the team that helped keep Google’s servers running smoothly, moved quickly to give his new team the ability to find the bottlenecks. Within days, the office in Maryland had big flat-screen TVs on the walls, each one showing the data flowing across the HealthCare.gov servers.

“It’s easy just to order a bunch of machines and install them, and we’re doing all that stuff,” Mr. Dickerson told a reporter at the time. “But you have to find exactly where is the choke point, and it’s a very compacted system.”

Mr. Dickerson compared his job to that of a traffic engineer who tries to identify bottlenecks in order to add capacity where it is needed and make things easier for drivers.

“You can add lanes to the freeway, but maybe that makes commute times better, and maybe it doesn’t,” he said last November. “If everybody backs up on the on-ramp, it doesn’t matter. It’s very much like that, but harder, because you can’t see with your eyes where all the cars are stopped.”

Officials said Mr. Dickerson’s team would start small, in part because of the need to use money already allocated to the government’s technology budget. There is $3 million in the current budget to use for that purpose, officials said, and $13 million has been requested for next year. The administration hopes to hire as many as 25 people.

In an interview on Monday, Mr. Dickerson said his team would intervene in situations in which websites needed acute attention and quick triage to make them work effectively. But he also said he would try to anticipate problems that might emerge and make fixes.