Tech & Innovation Blog
Roberto Masiero, SVP Innovation, talks about his journey from entrepreneurship to founding ADP’s first Innovation Labs.
Senior Leader, Innovation, Career Journey
We decided to open the first lab in Porto Alegre, Brazil, with a specific goal: to develop new products as quickly as possible.
After starting his career as an entrepreneur in Brazil, SVP of Innovation, Robert Masiero first came to ADP 20 years ago through an acquisition—and he’s been building new technologies here ever since. Below, he reflects on what led to the founding of the ADP Innovation incubators in Brazil and the U.S., explains the beliefs that shape his leadership style, and shares the cutting-edge challenges the team is taking on next.
First, tell us about your background and what brought you to ADP.
I started working in technology while I was in college as a mainframe operator on the overnight shift. I didn’t get much sleep! After that, I learned to code and became a developer, then did mainframe support. I had this urge to start my own business—and I did a few times. The first two failed, but the third one, a consulting company that transitioned applications from mainframes to open systems like Linux and Unix, did well. Eventually, we decided to create our own software for things our clients needed, things like HR, payroll, and accounts receivable.
That software went through several iterations, from character-based to client-server, Windows-based to the web. That was the mid-90s, and it was unusual to have software that could run in a browser, so large companies started showing interest. We added team members, but eventually, our product outgrew our business—we needed to expand our sales force, distribution support, and ability to do on-site implementations. At the time, there was no venture capital in Brazil; your only options were getting a bank loan or finding a partner. So we started going to trade shows. At one of them, we knew ADP would be two booths down from us, so we made sure to get their attention—we had this big TV screen showing all our client logos, many of which were also ADP clients. That started a conversation, and ADP ended up acquiring the business.
What was it like to integrate into such a large company?
I remember thinking we had a massive opportunity to succeed because, back in those days, ADP had mostly manual processes—people called or faxed in their payroll. So, in our first six months, we took the software we’d built for our clients to use and built a layer on top of it that allowed ADP to run things on a client’s behalf. We were just this tiny new acquisition, and ADP was very conservative at the time, so when we presented the updated software we’d created, I wanted to put on a big show. I rented a hotel ballroom, even though I didn’t have the budget for it, and I invited the entire leadership team.
They gave us a couple of large clients, and that turned out to be transformative. After a while, ADP shut down their mainframes in Brazil and moved those clients to our software—including GPA, which is like the Wal-Mart of Brazil, and the largest single payroll we ran globally. The complete transition took a few years. When we were done, ADP’s U.S. leadership team sent their CTO down to take a look; I think they weren’t quite sure it was real. But he liked what he saw—clients were happier, costs were down—so they invited me to move to the U.S. and adapt the software from a new tax credit services acquisition.
You started the first ADP Innovation Lab around that time. What led to that one—and the second lab?
We decided to open the first lab in Porto Alegre, Brazil, with a specific goal: to develop new products as quickly as possible. At the time, I was more familiar with the talent there than in the U.S. In Brazil, I could build a team of people I already knew, who were already familiar with the technology we wanted to use. So, ADP’s primary development team handled payroll, while we had a small team that focused on the tax credit work.
After the project was over, ADP invited me to run a Shared Services team of 700 people who handle identity management, the enterprise service business, and our internal associate portal. Then I moved over to Enterprise Architecture for a while. But I still had an entrepreneurial drive. About a decade ago, I went to ADP leadership and said I wanted to build an Innovation Lab here in the U.S. to focus on incubating completely new ideas. They said, “Okay, let’s do it,” and they gave me a team of four to get it started.
Tell us about some of the projects that the lab has developed.
We launched around the time the iPhone came out, so our first project was ADP Mobile. We put it together in about a year, and we used modern database tools like MongoDB rather than the Java- and Oracle-based ones that were typical at the time. We also built it for everyone; small businesses and multinational corporations could use it, and it worked in every country and supported 40 different languages. It grew very well—I think we reached a million users in less than a year. But I’d said from the start when we created that lab. I wanted to keep it small and flat, never more than 30 people, which meant when a project reached a certain level of maturity, it would “graduate” from the lab and get a dedicated R&D team. That’s what we did with mobile, which now has something like 25 million users.
After that, we worked on the tablet application and then built out semantic search, which we now use across ADP’s core products. The most recent project that graduated from the lab is ADP Marketplace, a collection of HR solutions that clients can customize and integrate with our software. The latest product we developed is called Roll™, which required an entirely different way of thinking about our services. Roll™ is a 100% mobile chatbot platform that simplifies payroll using state-of-the-art AI and natural language processing technologies. It can intelligently alert a client when something needs their attention—it’s an unprecedented level of automation.
What do you think makes a good leader?
In part, I think it’s about completely understanding the work your team is doing. When you’re running a large organization, of course, it’s also about who you put in charge—you have to trust your direct reports to make the right decisions. But even when I was leading hundreds of people in Shared Services, I still wanted to be familiar with the processes and skills they needed to do their jobs.
I never want to micromanage, but I do want to be hands-on and in the know. It’s leading by example—if there’s a production issue, for instance, I’ll be on a late call with the team. People appreciate it when you’re committed to their ideas, and they can trust you to have an educated conversation about the decisions that need to be made, whether that’s around technology or go-to-market strategy.
A good leader also ensures everyone on the team has a voice, whether they have ten days of tenure or ten years. In fact, the untrained eye of someone who’s starting their career can be a phenomenal asset to the rest of us. If you have an opinion or see something we could do differently, it’s so important that your input be heard and considered. Ultimately, we have to be pragmatic in our decision-making, but I love debate. I love being challenged and being proven wrong. The push and pull from many different perspectives makes this work fun.
What’s challenging about your work?
The toughest thing for any leader is making difficult decisions that affect other people. If you’re letting someone go, for example, even if it will be healthier for everyone involved, that’s very hard.
ADP’s size can also be a challenge because change is difficult for any big company. But I see that as an opportunity: If something has been done the same way for decades, let’s ask why. How could we change that process to make it more efficient? ADP is exceptionally open to challenging the status quo. Our people have the incentive to challenge existing ideas and revisit how things are done to find opportunities to improve or design for better outcomes. Just as I like my team members to challenge my assumptions, we get the same message from the very top of the company: If you see a better way, a chance to transform the way you work, you should be able to do that.
What’s exciting to you about ADP’s future?
I’m excited for us to continue investing in new ideas to make the lives of our clients and ADP associates better. We’re going through a period of significant change, and that’s never without challenges. But the level of commitment I’ve seen keeps me hopeful. We’re doing our small part in the lab with products like Roll™, and that’s just a portion of a company-wide effort to deliver on new technologies and innovations. All of us are committed to success and meeting our clients’ and associates’ expectations with innovative products and technologies that will have a phenomenal payoff and carry us through many years to come.
Tech & Innovation Blog
ADP Wins 2020 Breakthrough AI Award
Recognition, Artificial Intelligence, Data Science
Accessible Video Controls
Video: AI and machine learning to help our clients
[TEXT] Welcome to ADP DataCloud
[DESCRIPTION] In animation, a man speaks.
[TEXT] Hi, I’m Jack. I’m excited to share some of the recently launched DataCloud Features that are helping our clients navigate the Dynamic Workplace.
[DESCRIPTION] The word “Start” on a screen. Underneath it, the numbers 1 through 4. Jack touches number 1.
[TEXT] We’re helping Organizations Understand how their workforce has been impacted by Covid-19. How? Data Mashups. Data Mashups – Covid Workforce Impact. Data Mashup refreshes daily, displaying the # of Covid-19 cases documented by Johns Hopkins. This has helped organize and understand how their workforce has been impacted by Covid-19.
[DESCRIPTION] Jack presses 2.
[TEXT] We’ve identified Millions in tax credit opportunities for our clients. How? Say Hello to Storyboards. Storyboards – Employee Retention Tax Credit. Storyboards helps clients easily identify if they are eligible for Employee Retention Tax Credits. The platform will automatically calculate the tax credit opportunity based on eligible employees. E.R. T.C. has proactively surface to millions and tax credit opportunities for our clients.
[TEXT] 3. We are helping millions of Practitioners monitor employee sentiment about returning to the workplace. How? Meet Return to Work. Return to Work – Readiness Survey. Practitioners can now send short surveys to collect worker Readiness and sentiment about returning to the workplace. Surveys are delivered to workers through the easy-to-use a. D. P. Mobile app. Practitioners are monitoring employee sentiment about returning to the workplace.
[TEXT] 4. We’ve helped Practitioners Answer key questions about their organization. How? With Organizational Benchmarks. Benchmarks – Organizational Benchmarks. Clients can take a deep-dive into their organizational data and benchmark their company against peers. Uncover organizational questions like what percentage of labor cost do my peers spend on sales and marketing. Discover how their head count breakdown compares to their industry. ADP DataCloud, Learn, Get Inspired, Join the Conversation
Congratulations to our DataCloud team! Recognized for its impressive capabilities and significant value it brings to businesses, ADP’s DataCloud won a 2020 AI Breakthrough Award in the “Best AI-based Solution for Data Science” category. Watch the video.
In a constantly shifting world of work, businesses, now more than ever, are looking for a solution that helps them make informed decisions about their organization. Enter ADP DataCloud, a powerful people analytics solution.
Utilizing Artificial Intelligence (AI), the solution analyzes aggregated, anonymized HR and compensation data from over 30 million workers in more than 730,000 organizations to allow companies to benchmark and compare compensation data, turnover rate, and overtime. Endless possibilities open for better managing a global workforce when pairing this empirical data with the power of machine learning (ML) and AI.
The AI Breakthrough Awards recognize the top companies, technologies, and products in the Artificial Intelligence industry today. As more and more companies join the growing global AI market, this awards program honors those that stand out among a crowded field of competitors. In other categories, winners included IBM, Capital One, NetApp, and others.
Congratulations to the team for all your hard work to deliver amazing solutions and real-time trends to our clients. Way to break through!
Tech & Innovation Blog
Brazil Lab’s Carlos Nascimento Wins First Round NASA International Space Apps Challenge
Voice of Our People, Recognition, Innovation
Creating something out of this world almost came naturally to Carlos Nascimento, literally while he slept. Read about his innovation here.
Carlos recently won the first stage of the NASA International Space Apps Challenge. Yes, that NASA – the National Aeronautics and Space Administration…
Carlos developed a solution responsible for dynamically organizing the entire circadian cycle of astronauts, using Convolutional Neural Networks, being able to interpret brain frequencies, predict and stimulate the next stages of sleep.
“I could not have done this without the experience and knowledge I earned by working at ADP Brazil Labs,” said Carlos. “At the innovation center, we are working on a project that uses machine learning, which gave me the necessary knowledge and inspiration that I used for the NASA competition.”
NASA’s hackathon was the largest globally to develop an innovative app for its astronauts. With only 48 hours of active development, Carlos decided to focus on machine learning and brain signals. He gathered a team of his friends to select the challenge. They thought: “You know what? Everybody has some kind of sleep problem! Let’s help with that!”
Carlos will represent Brazil on the global stage, where they will choose the six best solutions.
At ADP, Carlos and his team work on a product that leverages machine learning. According to Carlos, “The best thing about working with Machine Learning is that the field is always evolving with new ideas and updates.”
Before Carlos travels to spaces and places, we caught up with him to learn just a little bit more:
What advice do you have for someone looking to participate in a global challenge?
These events are about innovation and teamwork, so choose your team wisely with professionals from different fields like designers, developers, and data scientists and read a lot about the subject you plan to solve.
What is your must-have app personally?
Brave Private Browser. We should always be very careful with our data. Like we are at ADP.
What is your favorite movie?
Interstellar.
If you could only eat one food for the rest of your life, what would it be?
Chocolate. I probably wouldn’t live much, but it would be a happy life.
What is the best advice you ever received?
Treat everyone the way you would like to be treated.
What’s the best place you’ve ever traveled to on vacation, and why?
That would be Arraial do Cabo. It’s close to my hometown, Rio de Janeiro. It has the most beautiful beaches I’ve ever seen.
Carlos will receive an award from the U.S. Embassy in Brazil for his work in the NASA Challenge. Results for 40 finalist teams, and six winning global teams, will be revealed in January 2021!
Congratulations, Carlos! Good luck to you and your team in the next round!
Learn more about working at Brazil Labs.
Tech & Innovation Blog
Race Against Time: How ADP’s Product Team Helped Thousands of Businesses Secure Critical Paycheck Protections Loans
Pandemic, Innovation, Voice of Our People
Bill and Terri look back on a whirlwind weekend in April, when the Small Business Administration (SBA) had launched an unprecedented new loan program established by the Coronavirus Aid, Relief, and Economic Security Act (CARES Act). Here’s their story.
In the wake of COVID-19, ADP’s product teams have worked tirelessly to ensure our clients weather the storm. We wanted to catch up with two of the people who’ve made this possible. Bill Leonard, Director of Product Management, was once the payroll director for ADP. He advises early-in-career colleagues to say yes to new opportunities—it’s brought him to where he is today. Terri Thomas, Senior Director of Product Management, says that she owes her 35-year career at ADP to outstanding mentors and the advice she received from day one: Don’t be afraid of what you don’t know.
Below, Bill and Terri look back on a whirlwind weekend in April, when the Small Business Administration (SBA) had launched an unprecedented new loan program established by the Coronavirus Aid, Relief, and Economic Security Act (CARES Act). Tens of thousands of companies applied in the first hour alone. Thanks in part to our team’s hard work, many loans went to ADP clients in the first funding round.
Take us back a few months when you first got involved in this project. How did it start?
Terri: I remember I got a phone call the day the CARES Act passed, the last Friday in March. The SBA would start accepting loan applications under the new Paycheck Protection Program (PPP) the following Friday. We wanted to be there for the thousands of ADP’s clients we expected to apply for the loans and give them the tools they would need to help their employees. That meant they needed information from us as soon as possible. I was asked to take the lead on the product side.
We had already been working on the provisions of the FFCRA, or Families First Coronavirus Response Act, which had passed the week before and potentially affected all 600,000 companies who use ADP. But the impact of CARES was massive, too, and we had far less time to take action. So, there was no debate, no red tape. We just got on a call and started working.
Bill: Absolutely. There was limited funding, especially in that first round, so our clients all wanted to be ready the minute the application period opened. We wanted to have their payroll cost reports and other supporting documents ready by Monday.
There were a couple of factors that made that difficult. For example, loan amounts were based on each employee’s annual payroll cost but capped at $100,000 per person per year. We couldn’t just pull data and run a report. The number of moving pieces was pretty astounding due to the rapid shifts in the regulatory environment with unnaturally compressed timelines. We had to respond just as quickly to ensure our clients could keep up and continue to thrive. We had a clear objective; we knew what we needed to do. I think ADP is at its best when we have a dragon to slay.
What were those first couple of days like before the project went live?
Bill: First, we needed to interpret the regulations. We received excellent internal guidance from ADP’s Legal and Compliance teams. They were fantastic in helping us navigate the regulatory language to figure out exactly what it all meant. We couldn’t make any assumptions—for example, defining full-time equivalent hours for employees. In the Affordable Care Act, that meant 30 hours per week, but in this legislation, it was 40.
Since ADP serves so much of the market, we had support at the federal level to ask questions and get answers quickly—and in some cases, we even made recommendations that helped shape the SBA’s guidance.
Terri: Agreed; our Legal and Compliance teams were amazing. The government would release something at 1 a.m. that we’d have to translate the logic of it, to see whether it changed what we were doing, and Legal was right there with us. FTE and lookback periods were big ones, and we also had to figure out what costs qualified, in terms of retirement and health care, and wages. Plus, there was a whole other set of guidance to interpret when it came to loan forgiveness.
ADP has such a large, diverse group of clients—everything from multinational corporations to pizza shops—we offer many different products to our client base. We had to find a way to produce reports that accommodated all those differences but were still consistent enough that a lender’s API could pull out the information they needed. So there were many conversations regarding which fields to “lockdown” and which to let clients edit. For example, if an employee doesn’t come back to work because their job is eliminated, the portion of a PPP loan based on their payroll cost usually isn’t forgivable. However, if an employee has the option to come back to work and refuses, it is. So, we had to build options for clients based on their unique situation.
What happened once the reports were posted—and what’s happened since?
Terri: In the first couple of days after we launched, clients relied on us to help them navigate the calculations. We explained why the numbers on our reports were different from the gross wages they saw on their regular payroll reports—and why they were supposed to be.
One thing that helped, though, was that we’d been able to quickly create not just the reports but some FAQs and other collateral. We shared that with our clients and our Service teams. I think those resources were a big key to our success. We got so much positive feedback from people saying how relieved they were to log on Monday morning and see that we were already on this. They didn’t have to go searching for answers.
Bill: Yes, I think from the client’s point of view, the most valuable thing we gave them, especially in that first week, was assurance. Many business owners were really scared—imagine your company’s entire existence is in question, and here’s this possible lifeline, but you don’t know how or whether you can actually use it. We were able to say, “We’ve got it; we’ll help you through this..”
Terri: Also, while we’d had to make some executive decisions internally to get through the initial launch, we immediately shifted into getting external input. We were pulling everyone into working sessions—clients, CPAs, banks—to find out what they thought about every aspect of the project and how we could do things even better. We kept iterating based on that feedback coupled with the government guidance that continued coming in. We’re still tweaking things even today.
What did you learn from this project that will help you going forward?
Bill: I think this project was an excellent example of keeping things simple. As Terri mentioned, ADP has lots of different products and tools, and for a good reason—we have many different clients. When we simplify, the easier it is to deploy new features and enable innovation. When things like this happen, it needs to be easy, innovative, and quick to market. Most of all, it needs to be right for our clients.
I also learned a lot about—and from—our team. There were many times when Terri and I and the rest of the people leading this project would talk something through, and then a developer would come back to us with a question that was complete gold and entirely changed the way we’d been thinking.
Terri: I couldn’t agree more. It doesn’t matter what your role is; if you have an idea or a suggestion, we want your voice to be heard. Innovation happens here at all levels, and the feedback is immensely powerful in moving the company forward. I’ve already seen numerous examples, and I’ve only been in this role for a few months. My goal as a leader is to encourage that as much as I can.
In true ADP style, the collaboration we saw between teams was amazing. Nothing was about titles or who was attached to what product. The difference this time was that people who don’t ordinarily work together teamed up to make this happen, and having all of those unique perspectives at the table was incredible. Our shared purpose is something I really love about ADP. We’re all working toward the same goal of making an impact for our clients.
In closing, Terri and Bill, you’ve been here 35 and 27 years, respectively. Would you share how you’ve seen ADP change and what advice you would give new people starting with ADP?
Terri: I had some fantastic mentors, and they pushed and made me think about the different opportunities. The advice given to me from day one was don’t be afraid of things you don’t know. That stuck with me for 35 years, and I leaped into things that I never thought I’d even consider. You control your own destiny. Nothing is just handed to you. I got myself in the door and continued to drive my career into different areas. It took a lot of hard work, but I was dedicated to doing it and have had many supporters. So, to me, the sky is the limit at ADP. You don’t have to be stuck in one area. You can go anywhere. It’s like taking a new job when you transition to your next role.
Bill: There is a lot of runway for people on the technology side these days. If you wanted to go into management, there has always been plenty of room there. Today, there’s been much more opportunity to stay on the technology side without having to move into people management to grow your career. As an example, this year, we named our first Distinguished Engineer.
Tech & Innovation Blog
Next-Gen Payroll Captures the 2020 Top HR Product Award
Recognition, Awards
ADP’s products continue to earn awards at a time when our clients need our innovative products the most. We are proud to be named a “2020 Top HR Product” by HR Executive.
ADP’s products continue to earn awards at a time when our clients need our innovative products the most. We are proud to be named a “2020 Top HR Product” by HR Executive.
ADP’s Next-Gen Payroll Platform enables companies of all types – from local small businesses to global conglomerates – to pay their employees their way. This real-time global payroll platform gives clients and their employees unprecedented transparency into how they are paid, along with predictive insights and suggested actions. Companies no longer need to guess the impact of regulatory changes but can proactively model these changes in real-time and plan for the future. At the same time, employees, contractors, and gig workers all have complete visibility into how their pay is calculated along with actionable tips on improving their financial wellness. Who couldn’t use that?
Built natively on the public cloud, this real-time global payroll platform:
- Gives practitioners and employees unprecedented transparency into how they are paid;
- Empowers practitioners to more easily understand the effects of regulatory and policy changes, enabling a stronger strategic partnership with business leaders by demonstrating bottom-line impact; and
- Delivers a breakthrough employee experience with predictive insights to model and understand the effect of potential life changes.
Winning solutions at the HR Technology Conference are selected based on several criteria, including their level of innovation, value-add to the HR professional, intuitiveness for the user, and ability to deliver on what they promise.
Tech & Innovation Blog
Time clocks in the age of COVID-19: How ADP developed a (mostly) touchless solution in just a few weeks
Pandemic, Innovation, Voice of Our People
In early March 2020, as the COVID-19 outbreak started to expand throughout the U.S. and Canada, the team working on ADP’s new Time Kiosk system started getting the same question from many of our clients: “Is there a way to use this without touching it?”
By Jonathon Gumbiner, Senior Product Manager
In early March 2020, as the COVID-19 outbreak started to expand throughout the U.S. and Canada, the team working on ADP’s new Time Kiosk system started getting the same question from many of our clients: “Is there a way to use this without touching it?” At the time, we were several months into a pilot program for the tablet-based timecard management app with more than 1,000 clients.” But most of them hadn’t adopted the app’s facial recognition feature, instead opting to tap in their badge number. And even for those who did use facial recognition, Time Kiosk still required each worker to tap the screen—a suddenly dangerous proposition during a global pandemic.
For companies that had essential workers on-site, we suggested an immediate but imperfect solution: low-cost touch pencils each employee could use to navigate the app. But we knew we’d ultimately need an integrated, turnkey option—and we’d need it as soon as possible.
After a quick brainstorm, we narrowed in on the fix that seemed most promising: First, we’d reconfigure the app to perform facial recognition by default, whenever someone was in front of the camera. Then, we’d use the tablet’s built-in virtual assistant, which powered features like Siri and Google Assistant, to respond to voice commands within Time Kiosk. If we were successful, employees would be able to start a workday, take lunch and other breaks, and clock out, all without touching the screen.
Within a couple of days, our developers were able to build a rough proof-of-concept. It was clunky and far from intuitive—to clock in, for example, you had to say “tap clock in” instead of simply “clock in.” But it was enough to help our senior leaders understand our vision for a more-refined solution—one that would meet the high standards we’d set for the original Time Kiosk experience. We got their buy-in and started to build.
Voice recognition was the first challenge. For one thing, as anyone who’s used a virtual assistant knows all too well, there are phrases it just won’t recognize. Also, in order to release the touchless features as part of Time Kiosk’s formal launch in both the U.S. and Canada, which was just a few weeks away, we needed to develop voice recognition for not only English but Spanish and French, as well—languages no one on the team speaks. Thankfully, as a global company, our partners from other ADP teams came to our rescue, helping us quickly create a repository of words to which the tablets would reliably respond.
Of course, we couldn’t make every action completely touchless. Switching between an employer’s custom job or department codes, for example, would require an employee to scroll through options that voice recognition likely wouldn’t cover. But what we could do was keep people informed. With the help of our UI team, we developed a treatment to add an icon for every touchless function, so employees could see at a glance whether they’d need to touch the screen. If so, they could wash their hands or take other precautions before they acted.
Once we’d finished the first phase, though, we came to a larger challenge: quality assurance. We spent twice as much time testing the new touchless features as we’d spent building them, going through every single action a user could take to make sure we’d identified everything properly. Because voice recognition touched the entire product, we had to review it all—and quickly, requiring a true team effort from QA. What’s more, we happened to be in the middle of transitioning to a new UI, so we needed to test both the current and the incoming interfaces, making the process twice as long.
Yet perhaps the biggest challenge of all was the pandemic’s impact on how it got done. To make sure the new features worked well in all three languages, we needed service reps and tech partners to help us with testing. But most of ADP’s 58,000-person team was working from home. I couldn’t simply walk upstairs, hand someone my tablet loaded with the latest version of our work and ask them to play around with it for a while and bring it back at the end of the day. Instead, we had to find a way to get it on their tablets remotely—no easy task given the tablet’s security restrictions. Luckily, our team was able to build a package and set of instructions that I could share, allowing partners to offer live feedback via an embedded diagnostic tool. They were invaluable in helping us fine-tune, especially our translations.
In the end, thanks to the hard work of everyone on the Time Kiosk team and many of our colleagues, we were able to meet our goal, transforming the app into an intuitive, mostly touchless experience in a few short weeks. Like any quick-turn project, it wasn’t without a few bugs. But the team’s rapid response to client questions and weekly Q&A calls have helped us not only serve their needs and build stronger relationships with them. Time Kiosk has now officially launched, and our sales teams tell us the touchless technology has been a conversation driver with both clients and prospects.
Even after the COVID-19 outbreak has passed, we see great potential in what we’ve learned about voice and facial recognition, whether it’s better accessibility for employees with disabilities or voice biometrics for authenticating service calls. In the meantime, we’re proud to say that when our clients had an urgent need, we were able to quickly deliver a solution that works—and that’s helping keep thousands of their people safe.
Jonathon Gumbiner is a Senior Product Manager at ADP in New Jersey.
Tech & Innovation Blog
How ADP leveraged new technology to help users affected by COVID-19
Pandemic, CARES Act, Helping Clients
When the Coronavirus Aid, Relief, and Economic Security Act, or CARES Act, became law on March 27, 2020, teams across ADP had already been hard at work for weeks preparing for the flood of new policies tied to this legislation. Here’s an example of how Cary Feuer and his team jumped to our clients aid.
By Cary Feuer, Director of Product Management, ADP Small Business Services
When the Coronavirus Aid, Relief, and Economic Security Act, or CARES Act, became law on March 27, 2020, teams across ADP had already been hard at work for weeks preparing for the flood of new policies tied to this legislation. In Retirement Services, we’d started with the simplest—and highest-impact—changes, such as initiating loans and withdrawals for users affected by COVID-19. By mid-March, we had successfully worked through those immediate projects and then turned our attention to a provision we knew would be much trickier: payment suspensions for 401(k) loans.
Since long before the pandemic, the IRS had allowed 401(k) owners to borrow money from their accounts for what it deems “immediate and heavy financial need,” such as a medical expense or a looming foreclosure. Now, under the CARES Act, borrowers affected by COVID-19 could choose to pause payments on those 401(k) loans until 2021. We knew up to 175,000 ADP users might qualify, and their average monthly payment was $800—a significant amount of money for many families. And we also knew that if even 10% of that group decided to suspend their payments and had to call us to do so, it would likely put a significant strain on our team. More importantly, it would be a headache for users during an already-difficult time. We wanted to give them an easy, self-service option, instead of making them wait on hold.
It was clear we needed a technical solution. But speed was critical—and because suspending payments is a multistep process (including self-certification of COVID-19-related hardship)—it wouldn’t be as simple as checking a box. On the backend, we needed to update money-movement databases and multiple payroll products, reamortize the loans, and create an audit trail, all of which we knew we could do relatively quickly. On the frontend, though, we would normally take our time on development and testing, ironing out every wrinkle to ensure the best user experience. A UI build of this scale might take several sprints to ship across mobile, web, and legacy web platforms. In this case, we didn’t have that long.
Instead, we turned to a new piece of third-party technology, which ADP had recently integrated to allow for faster deployment of simple features like pop-up guides and mini-surveys. Designed for product managers and others to use without the help of an engineer, this technology offers templatized, customizable design patterns—and it had already been vetted by ADP’s Technical, Security, and Legal teams. It was our best, and perhaps only, option to get the frontend of payment suspensions up and running on an accelerated timeline. However, because of all the backend changes each payment suspension would trigger, we’d need to learn how to work with the product in an entirely new way, pulling information out of its API and into our own infrastructure.
Our lead developer joined with our lead development team for a quick feasibility study, and within a couple of days they’d determined our plan could work. So, with added help from one of ADP’s resident experts on the 3rd party software, we all got to work building. Our colleagues in Service Ops helped us develop the content, a UX teammate gave the frontend flow their blessing, and in less than two weeks we were almost ready to ship.
But then we ran into a snag. In order for the third-party product to know which users should see a payment suspension option, it needed to refer to a list of qualified users’ anonymized IDs—and with so many people facing financial hardship and taking out new 401(k) loans, that list was changing every day. Because of the time crunch, we’d decided to upload up-to-date CSVs of user IDs to the product each morning by hand. But this seemingly simple fix was a use case that the product—a relatively new technology still in its startup phase—wasn’t built for. Each day’s upload was taking hours to complete.
Rather than delay the release, we decided to ship our new feature and keep handling the CSVs manually. Contemporaneously, we started work on a mini-app that could automatically break up and upload the CSVs. After a few days of testing, we finally had a feature that was not only fully self-serve for our users, but fully automated for us. Thousands of people have now paused their loans without needing to call in, saving them time and potential frustration—and saving ADP the equivalent of adding two full-time employees. Over the course of the program, our uploading solution will save hundreds of additional hours.
Meet Cary’s four-legged office mate
Even better, our team is more familiar with a brand-new technology that we can now leverage in other creative ways. The next time we’re responding to a fast-developing situation, such as a hurricane, we’ll have this 3rd party technology in our toolbox. We’re currently validating it for other use cases, where time to market is less of a concern. With just a few weeks of work, we were able to expand our team’s development toolset, better serve our users when they needed it most, and make an investment in the future of ADP.
This is just one way that our tech teams have added new tools into our tech stack. This feature is now available for all ADP Retirement Services clients that offer CARES Act provisions to their employees.
Cary Feuer is a Director, Product Management for Small Business Services at ADP and is based in New Jersey.
Tech & Innovation Blog
ADP Leaders Make Top 100 HR Tech Influencers List
HR Tech Influencers, Senior Leaders, Recognition
With an eye on innovation and transformation, two ADP leaders have once again earned a coveted spot on the second annual Top 100 HR Tech Influencers list released by Human Resource Executive®.
Marcus Buckingham
Don Weinstein
That’s right. For the second year in a row, Marcus Buckingham, Senior Vice President and Co-Head of the ADP Research Institute, and Don Weinstein, Corporate Vice President for Global Product & Technology at ADP, have made this list. The list includes leading thinkers from across a wide variety of business functions – executives, advisors, consultants, analysts, implementers, and many more. ADP is one of just a handful of companies to have more than one influencer on the list.
Across the board, this collective group was heavily evaluated on a wide range of criteria and measured on their record of influence amongst Human Resource (HR) organizations. The individuals on the HR Tech Influencers list have a high reputation for unique strategies, innovative solutions, and bring a positive influence on today’s HR-tech marketplace.
Join us in celebrating and honoring both Marcus and Don on making this list for the second year in a row. Their contributions towards innovation continue to propel ADP’s transformation into one of today’s most forward-thinking technology companies.
Being on the list showcases our continued focus on developing innovative technology to help our clients when they need it most. According to Human Resource Executive, “The work that lies ahead will need the unique human touch that only HR can provide—and that approach can be magnified by the deployment of smart HR-technology solutions.”
Creating human-focused solutions in today’s product strategy
ADP Business Anthropologist Martha Bird sat down with Daniel Litwin, the Voice of B2B, at CES 2020, discussing a wide range of topics related to how her anthropological work and research impacts businesses and consumer needs.
Bird has worked for numerous companies in the field of business anthropology since the early 2000s, working to create human-focused solutions to business needs.
Bird and Litwin touch on their CES experience, a modern focus on human-centered and human-responsive products and how those concepts affect consumer product development, consumer longing for personalized experiences, and more.
Lifion at ADP’s cloud transformation journey
https://eng.lifion.com/lifions-cloud-transformation-journey-2333b7c0897d
Lifion’s Cloud Transformation Journey
On moving to managed services in a microservice architecture
Since Lifion’s inception as ADP’s next-generation Human Capital Management (HCM) platform, we’ve made an effort to embrace relevant technology trends and advancements. From microservices and container orchestration frameworks to distributed databases, and everything in between, we’re continually exploring ways we can evolve our architecture. Our readiness to evaluate non-traditional, cutting edge technology has meant that some bets have stuck whereas others have pivoted.
One of our biggest pivots has been a shift from self-managed databases & streaming systems, running on cloud compute services (like Amazon EC2) and deployed with tools like Terraform and Ansible, towards fully cloud-managed services.
When we launched the effort to make this shift in early 2018, we began by executing a structured, planned initiative across an organization of 200+ engineers. After overcoming the initial inertia, the effort continued to gain momentum, eventually taking a life of its own, and finally becoming fully embedded in how our teams work.
Along the way, we’ve been thinking about what we can give back. For example, we’ve previously written about a node.js client for AWS Kinesis that we’re working on as an open source initiative.
AWS’s re:Invent conference is perhaps the largest global cloud community conference in the world. In late 2018, we presented our cloud transformation journey at re:Invent. As you can see in the recording, we described our journey and key learnings in adopting specific AWS managed services.
In this post, we discuss key factors that made the initiative successful, its benefits in our microservice architecture, and how managed services helped us shift our teams’ focus to our core product while improving overall reliability.
Why Services Don’t Share Databases
The notion of services sharing databases, making direct connections to the same database system and being dependent on shared schemas, is a recognized micro-service anti-pattern. With shared databases, changes in the underlying database (including schemas, scaling operations such as sharding, or even migrating to a better database) become very difficult with coordination required between multiple service teams and releases.
As Amazon.com CTO Werner Vogels writes in his blog:
Each service encapsulates its own data and presents a hardened API for others to use. Most importantly, direct database access to the data from outside its respective service is not allowed. This architectural pattern was a response to the scaling challenges that had challenged Amazon.com through its first 5 years…
And Martin Fowler on integration databases:
On the whole integration databases lead to serious problems becaue [sic] the database becomes a point of coupling between the applications that access it. This is usually a deep coupling that significantly increases the risk involved in changing those applications and making it harder to evolve them. As a result most software architects that I respect take the view that integration databases should be avoided.
The Right Tool for the Job
Applying the database per service principal means that, in practice, service teams have significant autonomy in selecting the right database technologies for their purposes. Among other factors, their data modeling, query flexibility, consistency, latency, and throughput requirements will dictate technologies that work best for them.
Up to this point, all is well — every service has isolated its data. However, when architecting a product with double digit domains, several important database infrastructure decisions need to be made:
- Shared vs dedicated clusters: Should services share database clusters with logically isolated namespaces (like logical databases in MySQL), or should each have its own expensive cluster with dedicated resources?
- Ownership: What level of ownership does a service team take for the deployment, monitoring, reliability, and maintenance of their infrastructure?
- Consolidation: Is there an agreed set of technologies that teams can pick from, is there a process for introducing something new, or can a team pick anything they like?
From Self-Managed to Fully Managed Services
When we first started building out our services, we had a sprawl of supporting databases, streaming, and queuing systems. Each of these technologies was deployed on AWS EC2, and we were responsible for the full scope of managing this infrastructure: from the OS level, to topology design, configuration, upgrades and backups.
It didn’t take us long to realize how much time we were spending on managing all of this infrastructure. When we made the bet on managed services, several of the decisions we’d been struggling with started falling into place:
- Shared vs dedicated clusters: Dedicated clusters for services, clearly preferable from a reliability and availability perspective, became easier to deploy and maintain. Offerings like SQS, DynamoDB, and Kinesis with no nodes or clusters to manage removed the concern altogether.
- Ownership: Infrastructure simplification meant that service teams were able to develop further insight into their production usages, and take greater responsibility for their infrastructure.
- Consolidation: We were now working with a major cloud provider’s service offerings, and found that there was enough breadth to span our use cases.
Evolutionary Architecture
On our Lifion engineering blog, we’ve previously written about our Lifion Developer Platform Credos. One of these speaks to the evolutionary nature of our work:
- Build to evolve: We design our domains and services fully expecting that they will evolve over time.
- Backwards compatible, versioned: Instead of big bang releases, we use versions or feature flags letting service teams deploy at any time without coordinating dependencies.
- Managed deprecations: When deprecating APIs or features, we carefully plan the impact and ensure that consumer impact is minimal.
When we started adopting managed services, we went for drop-in replacements first (for example, Aurora MySQL is wire compatible with the previous MySQL cluster we were using). This approach helped us to get some early momentum while uncovering dimensions like authentication, monitoring, and discoverability that would help us later.
Our evolutionary architecture credo helped to ensure that the transition would be smooth for our services and our customers. Each deployment was done as a fully online operation, without customer impact. We recognize that we will undergo more evolutions, for which we intend to follow the same principles.
