We are so pleased to honor Women’s History Month by celebrating women’s achievements across Lifion!

Our aim for this series is to be a conversation starter and a way for us to bring attention to the countless women who have shaped and continue to shape Lifion’s success.

Please join me in celebrating Danielle Diago. Prepare to be inspired (and tag the women that inspire you every single day)!

Associate Name: Danielle Diago

Associate Title: Lead Product Manager

Why did you decide to pursue a career in technology?

My career in technology has been one of evolution. After graduate school, I began working in HR, specifically in Organizational Development and Shared Services. A few years later, I accepted an opportunity to work at small niche PEO in NYC as an HRIS analyst within their technology department. This is when my passion for technology was ignited. Throughout my tenure there, I taught myself how to read and write SQL, developed all their standard and custom HR/Payroll reporting and maintained all aspects of their ERP system. Towards the end of my tenure, I lead the implementation of a Business Intelligence system, helped construct their data model and later became the Product Manager. I didn’t intentionally launch a career in technology, but I’m incredibly grateful its where I’ve landed.

What has been your most memorable career-defining moment?

I would say I’m currently experiencing my most memorable career-defining moment. I have the incredible opportunity to help define what the future of Global Payroll is for ADP. This is incredibly exciting for me. I’m honored and grateful for this opportunity.

What do you think has made you an effective technologist?

My drive and commitment to push things forward. Making an effort to be proactive in everything I do. A saying that resonates with me is “How you do one thing, is how you do everything”.

Always trust your instinct and advocate for what you believe is the right solution.

What is one piece of advice your current self would tell your younger self?

Believe in yourself, trust your judgement and do not be afraid to voice your opinion.

Women’s History Month at Lifion was originally published in LIFION by ADP on Medium, where people are continuing the conversation by highlighting and responding to this story.

We are so pleased to honor Women’s History Month by celebrating women’s achievements across Lifion!

Today we’re celebrating Brianne Wilson. Prepare to be inspired (and tag the women that inspire you every single day)!

Associate Name: Brianne Wilson

Associate Title: Lead Product Manager

Why did you decide to pursue a career in technology?

Quite honestly it was an accident. I graduated from college right before the recession with a degree in theatre. Pre-recession days we were told, “As long as you have a degree, you’ll be fine.” The reality was much different. I’d get laughed out of job interviews for entry-level, minimum wage jobs because of my degree, even though it was from a prestigious school. It didn’t matter. Jobs were scarce and I was competing with people with 10+ years’ experience for the same job.

During my first few years out of college I moved from NYC to Chicago, and worked a lot of odd jobs while auditioning and performing. I didn’t have health insurance, had a mountain of student loan debt, and realized very quickly I was not making a sustainable living. A friend reached out to me about an entry level job in data analytics and sales operations, main requirement being good at Excel. From that one leg up, I got my first job in technology as a reporting analyst and system administrator in Salesforce for an AdTech company. I discovered I had a knack for it and kept saying “yes!” to taking on new projects and learning new skills. Writing intense excel formulas transformed into learning to code, which transformed into product development solutioning, which transformed into a career in technology. It’s also possible that this path was also just in my blood, as my mother was a computer programmer starting back in the early 70s (when women were the primary coders!).

What has been your most memorable career-defining moment?

About 8 years ago I was working at a software company where we designed and implemented solutions for workplace giving and grant management. My first project there, I was somewhat solo as it was the only project being developed on Salesforce. I was handed a 60 page requirements document on my first day and had to design and implement the entire solution from start to finish. When that project ended I was moved to the main projects of the company where I worked as a software developer. I loved that I had learned to code and loved telling people I was a female coder. We brought a consultant into the company as we were growing and needed to have processes change and improve. What was supposed to be a 15 minute meet-and-greet turned into a 2 hour discussion about my career path. I talked about how I missed my original project, how I loved the problem solving and solutioning. I loved figuring out what code needed to be written more than I loved writing the code itself. There were people at the company who loved coding and were definitely better at it; I liked everything leading up to my fingers on the keyboard. From there he asked me, “do you know what a product manager is?” I did not, as we didn’t have a product team at this very small company yet. When he explained what a product manager did, it was like everything fell into place that led to where I am now. I knew it was exactly what I wanted to do and the right place for me. I love sitting between the technology and the business strategy, and I love solving problems that lead to product features. Had I not had coffee with that consultant that day, I don’t know I would have ever fallen into product management!

What do you think has made you an effective technologist?

My theatre background! No really! Discipline, empathy, collaboration, communication, and analysis are all skills necessary to be an impactful performer and technologist.

Preparing a scene from Romeo and Juliet requires adept problem solving around literary devices and character development: Is this in verse or prose? Is this line 10 beats? 11? 5? Does this character use more vowels than consonants or vice versa? Is this a metaphor? Is this antithesis? This line is short, but not shared with the next character’s line, what do I think is happening here? I can go on. There are equations and problem solving in classical text that is really no different than putting together requirements for a product.

Then there’s the execution of it all. To be an actor, you have to be disciplined both in getting the job, and then helping make the show happen. Auditioning is a full time job you have to commit to and is full of rejection. Once you get the job, it’s a team effort barreling towards opening night. During the last week before a show opens, you’re pulling all-nighters, collaborating with everyone to make magic happen. Scenes are being re-blocked, costumes sewn together last minute, lighting cues to figure out, and so on. This is particularly true when you’re in training as you’re often playing stage crew, lighting ops, and sound in addition to performing. You do everything and anything to get a show on its feet. No job is beneath you and you stay until you get it working.

You want someone who is hardworking, a team player, and a good communicator who empathizes with their client? Hire someone who went to art school!

What is one piece of advice your current self would tell your younger self?

It’s okay to change your dreams.

For a long time I felt wary about being in technology. I didn’t want to love it and felt insecure because I hadn’t initially gone to school for it. I spent my entire life thinking I’d be one thing, and that wound up not being the path my life took. I constantly worried that everyone around assumed not that I was a successful technologist, but simply a failed actor. It kept me straddled between the two worlds, not fully committed to either. But once I accepted that I really just fell in love with a new dream, I realized every decision made and lesson learned in my old dream led me to this new one. And what’s more? I still perform in the theatre. Having a new dream did not erase the old, simply reshaped it!

Women’s History Month at Lifion was originally published in LIFION by ADP on Medium, where people are continuing the conversation by highlighting and responding to this story.

Our vision is to build the next generation of Human Capital Management tools — think payroll, benefits, HR and talent management — that let companies unleash the full potential of their people and become wildly successful. But we can only do this with the best talent.

Each month we’ll feature one member of the Lifion team here on our blog. It’s an ongoing look into the team that’s making our vision come true.

Vinodhkumar Manoharan — Lead Application Developer, Lifion Chennai

Joined Lifion: 2016 (joined ADP in 2012)

Prior to Lifion: I was working with Tata Consultancy Services for over 5 years wherein I played different roles starting from pl/sql production support executive, manual tester, automation tester and test lead. I was proficient in the Japanese language which helped me work on Japanese projects for over 3 years at TCS.

School: Panimalar Engineering, Anna University, Chennai

Team: Serenity

Serenity, I believe, is one of the first teams representing Lifion from Chennai. We built the ALM tool (Application Lifecycle Management) within the Lifion product which includes processes such as creating a miniapp, creating branches under the miniapp, performing all metadata developments under that branch, merging development changes into the master branch, promoting the miniapp into upper environments, etc. We were successful in building this process which enabled streamlined metadata development.

Currently we are working in the Metadata Test Tooling workstream. As part of this team, we are working towards creating a suite of test tools which helps us build a platform that holds core principles of quality assurance and governance.

Personally, the Serenity team (and Lifion) helped me build my career into a development lead from a testing background.

Most interesting problem you’ve had to solve at Lifion?

ALM versioning. To solve it, we came up with quite a number of scenarios. For example, should we allow patch version creation from a patch version of a mini app? Restrict creation of a minor version if a major version is released? How will patch version changes get merged to a new minor version of miniapp? It took lots of consideration to figure out the logic, which is why I found it so interesting.

Favorite mistake you’ve made here? How’d you fix it?

I tried to reproduce an Appbuild (the test environment our development team uses to create new iterations of mini-apps) issue in my DitC (DevOps in the Cloud) which had a different version of the service. For quite sometime, I couldn’t reproduce it. Later on debugging found that my services were old and I pulled the latest image to fix it.

If you could trade jobs for a day with anyone at Lifion, who would it be? Why?

I would trade my job with Lifion developer — just to understand the different ways of utilising the platform features.

Favorite tool you’re using here at Lifion?

Both the UI test tool and ALM.

When you’re not at Lifion, what are you doing?

I like spending time with my family, shopping, and traveling. I also like playing online chess and Speed driving.

Want to learn more about Lifion and what we’re up to? Click here.

LIFE AT LIFION was originally published in LIFION by ADP on Medium, where people are continuing the conversation by highlighting and responding to this story.

Our vision is to build the next generation of Human Capital Management tools — think payroll, benefits, HR and talent management — that let companies unleash the full potential of their people and become wildly successful. But we can only do this with the best talent.

Each month we’ll feature one member of the Lifion team here on our blog. It’s an ongoing look into the team that’s making our vision come true.

Mark Angelillo — Application Architect

Joined Lifion: Nov 30, 2016

School: Swarthmore College

Prior to Lifion: Worked on various startups in the media/tech/wine space

Team: Payroll NYC

Most interesting problem you’ve had to solve at Lifion?

How to avoid overindulging on the awesome snacks. Seriously though, the payroll domain is full of interesting problems to solve. Understanding the scenarios and challenges that a payroll practitioner faces and helping to make payroll software that is simple to use is an opportunity for us. We’re fortunate to be able to draw on a group of ADP veterans and experts who help us get up to speed quickly.

Favorite mistake you’ve made here? How’d you fix it?

During my first 2 weeks at Lifion, while working on my onboarding project, I was attempting to create a set of domain and adapter Mini-Apps. At some point I got myself into some kind of metadata-branch-override-dependency-paradox which blew up in dramatic fashion. Fortunately a bit of endpoint sleuthing and a clutch rescue from the Inception team dug me out of that one. I learned pretty quick that we can make great things and without proper care we can break those great things.

If you could trade jobs for a day with anyone at Lifion, who would it be? Why?

I would trade jobs with pretty much anyone at Lifion for a day, but it would take many more days than one to truly get immersed in a different workstream. I suppose for a single day anyone on the support team would have the most fast-paced, diverse and shifting set of challenges. I’m grateful for their hard work and would love to see a bit more of what they do to keep things humming along.

Favorite tool you’re using here at Lifion?

Definitely the platform itself. It has been awesome to watch the evolution of the tool even in the past 7 months. It really speaks to the strength of the team and I’m looking forward to seeing how it continues to evolve.

When you’re not at Lifion, what are you doing?

Chasing after a 14-month-old who seems intent on crashing around my apartment in the most dangerous way possible.

Want to learn more about Lifion and what we’re up to here? Click here.

LIFE AT LIFION was originally published in LIFION by ADP on Medium, where people are continuing the conversation by highlighting and responding to this story.

Our vision is to build the next generation of Human Capital Management tools — think payroll, benefits, HR and talent management — that let companies unleash the full potential of their people and become wildly successful. But we can only do this with the best talent.

Each month we’ll feature one member of the Lifion team here on our blog. It’s an ongoing look into the team that’s making our vision come true.

Mike Hirawady, Solutions Architect

Joined Lifion: July 2015

School: Lehigh University

Prior to Lifion: I was a Technical Product Owner for the Identity Management and Authorization team at a big cable company, building out the system for their customers to access their online properties as well as all the integrations with content providers.

Team: Mainly Cerberus and Morpheus although I am also involved in a few other workstreams. Cerberus is responsible for the Authorization system in Lifion. Morpheus is building out the Flex Structure product, which is essentially a graph database that can be used to model various relationships within the HCM domain (and more). Think Managers to Direct Reports, or Employees to their Authorization Grants.

Most interesting problem you’ve had to solve at Lifion?
Working on Flex Structure and figuring out the design-time experience for the Application Developers to query a graph database. Graph database itself is an interesting product to work on, the additional abstraction layer required to make it a Platform product makes it even more interesting.

Favorite mistake you’ve made here? How’d you fix it?
I’ve been at Lifion long enough to have more than one favorite. The important thing at Lifion is that we are encouraged to learn from our mistakes and find a solution to prevent the same mistake from happening again.

If you could trade jobs for a day with anyone at Lifion, who would it be? Why?
An Application Architect. The breadth and flexibility of the Platform we are building is amazing. I would find it interesting to architect an application ecosystem using only the Platform tools and features.

Favorite tool you’re using here at Lifion?
Most of the collaborative tools, although Google Drive is probably my favorite. These tools are indispensable in our culture where so many ideas and so much information is constantly shared with other people and teams.

When you’re not at Lifion, what are you doing?
Enjoying the outdoors, most likely with a camera in hand taking pictures of anyone and anything.

Want to learn more about Lifion and what we’re up to here? Click here.

LIFE AT LIFION was originally published in LIFION by ADP on Medium, where people are continuing the conversation by highlighting and responding to this story.

Our vision is to build the next generation of Human Capital Management tools — think payroll, benefits, HR and talent management — that let companies unleash the full potential of their people and become wildly successful. But we can only do this with the best talent.

Each month we’ll feature one member of the Lifion team here on our blog. It’s an ongoing look into the team that’s making our vision come true.

Onaney Barrino, Project Manager

Joined Lifion: December 13, 2013

School: Studied Engineering at Cooper Union and Culinary Arts at Johnson and Wales

Prior to Lifion: Worked in Finance for twelve years in Operations and as a Registered Sales Associate before the 2008 market crash. After the crash, I worked as an Office Manager until finding Lifion.

Team: Operations — the Gravitons.

Most interesting problem you’ve had to solve at Lifion?

In Operations, you solve problems on a daily basis. Having to choose just one would be like saying you could eat just one Lays chip. If you get this, you may be showing your age. :)

Favorite mistake you’ve made here? How’d you fix it?

Not regularly attending sprint demos sooner was definitely a mistake. Demos allow transparency for the entire organization, get everyone excited about what we are building, provide support for our teams, and help promote company culture.

The fix was that I started attending demos even though I could not understand most of what was presented. Eventually I began to understan what the engineers and developers were doing and how amazing it all was.

If you could trade jobs for a day with anyone at Lifion, who would it be? Why?

If I could trade jobs, then I’d also like to trade brains, because what I’d like to experience the most is how a truly creative mind works. How the thoughts flow once a spark is lit. With that in mind, I’d love to trade with a UX/UI Designer and see the process of how they create easy, enjoyable and valuable experiences for our clients.

Favorite tool you’re using here at Lifion?

Hands down, the ADP Mobile App. I love how I can access most of my work-related information in one place and from anywhere at any time.

When you’re not at Lifion, what are you doing?

Always doing my favorite things: spending time with my hubby and four kids or reading/binge watching sci-fi or fantasy.

Want to learn more about Lifion and what we’re up to over here? Click here.

LIFE AT LIFION was originally published in LIFION by ADP on Medium, where people are continuing the conversation by highlighting and responding to this story.

Want to hear more from Jason? He’ll be speaking at Microservices Day NYC on March 23rd about our journey creating a distributed platform where our technology focus, culture, and aligned patterns have driven our growth from a few individuals to a 300-person product and engineering-led technology organization active with production users in less than 2 years — all in the highly competitive HR and payroll industry. Video to follow!

Microliths: How to Avoid Traps in Your Stack & Your Culture was originally published in LIFION by ADP on Medium, where people are continuing the conversation by highlighting and responding to this story.

Our vision is to build the next generation of Human Capital Management tools — think payroll, benefits, HR and talent management — that let companies unleash the full potential of their people and become wildly successful. But we can only do this with the best talent.

Each month we’ll feature one member of the Lifion team here on our blog. It’s an ongoing look into the team that’s making our vision come true.

Nagaraj Danda, Lifion Developer at Lifion Hyderabad

Joined Lifion: 14th March, 2016

School: National Institute of Science and Technology, Berhampur, Odisha

Prior to Lifion: I was working with Wipro Technologies on various advanced Javascript libraries for building web-based applications, and using them to resolve real-time problems. These solutions were primarily focused on providing HR and operational solutions for customers in the energy and natural gas industry.

Team: Vulcan

I then joined the amazing Vulcans as a Lifion Developer. Team Vulcan is passionate about building robust, performant and core applications, and integrating those with other applications to facilitate free flow of data. We’re focused on providing innovative solutions to compensation-related challenges faced by our clients in their HR practice. Currently, we are working on Core Compensation integration with Payroll.

Most interesting problem you’ve had to solve at Lifion?

As mentioned above, we are in the process of building a Compensation application and integrating it along with Payroll. Our vision is to build smart, intelligent applications that provide insights, predictions and self-learning applications to the user, moving ahead of the conventional and traditional way of using Compensation.

One of the interesting challenges I took up was to develop a Compensation application such that it can live in an integrated environment alongside payroll and other domains, as well as survive standalone without any integration required. The data modeling and role-based user access to data for Compensation was something new to me and definitely interesting to master.

Favorite mistake you’ve made here? How’d you fix it?

Thanks to the team for creating a work environment so great that mistakes are usually believed to be the path to new ideas, innovation and new opportunities. And for my favorite mistake/s, my teammates put me in charge of photobombing lots of dubsmashes and birthday clicks :)

If you could trade jobs for a day with anyone at Lifion, who would it be? Why?

Given a chance, I would love to be a user experience designer for a day (or maybe more if they let me). The way UX designers think, how they design by improving the user interaction by taking a magnifying glass to every little detail inspires me. The creative ways of solving a problem, understanding the product, communicating the essence of the product to a user from a wireframe is really interesting. And special thanks for the “Midas touch” from the UX teams to make the apps perfect.

Favorite tool you’re using here at Lifion?

Our team has developed many plugins on top of the platform out of which my personal favorite is “Shape Browser.” What makes it my favorite is the way it works to provide an easy interface to fetch data, querying the database for records using our platform’s capabilities.

When you’re not at Lifion, what are you doing?

I take time out to travel and trek with my friends to remote places. My last trip was a crazy bike trip with my friends to the Ladakh region of the Himalayas. I play football when not at work, and I don’t mind some bowling over a pint of beer, either.

Want to learn more about Lifion and what we’re up to over here? Click here.

LIFE AT LIFION was originally published in LIFION by ADP on Medium, where people are continuing the conversation by highlighting and responding to this story.

Our vision is to build the next generation of Human Capital Management tools — think payroll, benefits, HR and talent management — that let companies unleash the full potential of their people and become wildly successful. But we can only do this with the best talent.

Each month we’ll feature one member of the Lifion team here on our blog. It’s an ongoing look into the team that’s making our vision come true.

Shayyan Arshad, Lifion Developer

Joined Lifion: July, 2016

School: NJIT — Business and Information Systems

Prior to Lifion: I was a Senior Integration Analyst at the New Jersey Innovation Institute, where I worked with a majority of Hospitals and Private Practices in New Jersey to facilitate the sharing of clinical data through a Health Information Network.

Team: I’m an LD on the payroll team!

Most interesting problem you’ve had to solve at Lifion?

I think the payroll domain as a whole has been an interesting use case through my tenure at Lifion. Seeing it evolve from its infancy, where we only had a few screens with limited functionality, to a fully functional payroll system that is currently paying employees is a testament to the platform we build on, and the team effort required to keep all the cogs moving. For example, a crucial part of our payroll system is the transmission of payroll data to payroll engines that process and pay the employees. This piece alone uses almost every aspect of the platform, from the input screens used to create and enter data, to ETL which transforms and converts the data to a format acceptable by the payroll engines. When implementing, we were able to iterate on the functionality we had already built, and in many cases, re-use objects we already built for other components of our payroll miniapps.

What does it mean to develop on the Lifion platform?

Lifion developers operate in a low code environment — we use a set of metadata driven developer toolkits which allow us to create complex business-facing applications without the need to code in the traditional sense. As a Lif Dev we spend the majority of our time working on the platform, building and enhancing our client-facing apps. Comparatively it’s very easy for our entire teams to simultaneously work on a feature set, and build it out in a relatively short amount of time. We’re able to accomplish almost anything using the platform as our tool instead of coding in a language like Java or Node.js. That said, it does take a couple days to get used to developing in the platform, but once you’re comfortable enough, it doesn’t take many sprints to roll out complex functionality, like Payroll.

How did you, as a Lifion Developer, work with the rest of the payroll team to implement the above?

When I first started at Lifion, I was very new to the HR domain. I had worked on problems with similar complexity, but as a whole, joining a team that has extensive collective knowledge about the domain, has an incredible dynamic, and is willing to help you grow is a recipe for success.

Favorite mistake you’ve made here? How’d you fix it?

I don’t think I have a “favorite” mistake. Any mistake I’ve made here has been a learning opportunity to better understand the payroll domain and the platform we use to deliver our functionality.

Favorite tool you’re using here at Lifion?

Apart from the coffee machines? I’d say my standing desk is one of the best perks and tools I use every day.

When you’re not at Lifion, what are you doing?

Usually, I’m home with friends or family. Definitely guilty of binging on Netflix and Amazon Video. Right now, it’s Voltron and The Grand Tour. :)

LIFE AT LIFION was originally published in LIFION by ADP on Medium, where people are continuing the conversation by highlighting and responding to this story.

At Lifion, we move fast and need to communicate quickly and effectively — especially in emails. Our own Max Kirchoff wrote a post on how to do it (really) well.

One of the biggest problems I face working in product and engineering groups is communication across an organization or groups of people in diverse roles. At a large company, like Google, I found it hard to get colleagues’ attention. My emails and notes were tiny droplets of water in the firehose of their inbox; there’s a reason Google keeps chasing better tools for email management.

When at smaller sized orgs, like The Bold Italic, I had a very different problem, as we had about 20 people, but our roles varied greatly from design to biz dev and engineering to editorial. The smaller audience made it easy to distribute comms, but the variety of backgrounds and perspective made it hard to craft messages that were easily understood, yet specific enough to provide value.

I knew that there had to be a way to address both the scale and the usefulness of the message to different, busy people. I honed in on the basics of crafting communication, email specifically. What I ended up with was a method that could get the right amount of attention, be useful to the reader, followed a pattern and was easy to repeat. These four aspects above end up being the litmus test of effective organizational communication in general — scale, scope, consistency and reproducibility.

This can also be outlined as the Recipients, the Subject line, the tl;dr, the Explanation, and the Ask. However, we should approach this list upside-down: start with the ask and end with the audience.

The Ask

This is the driving point of the email and the purpose you are sending it. If there isn’t a clear action or single point, then you need to ask why you’re writing an email at all. Drive at the one ask. What do you need the recipient to do? Leave this as a closing line that is concise but brief. If you need them to take action, wrap that up into a simple task or question that you can elaborate on in the Explanation.

The real keys here are to be brief and clear, but don’t forget the empathy as well. Speak to your recipient as you would in a face-to-face interaction.

The Explanation

This is the long-form aspect of your communication and should contain the most detailed information. Normally, readers will be reading this if they are the most affected by your comm, they are the experts of the topic, or they are simply interested. Do not be afraid of technical jargon here, but be able to explain it in plain English as well. Brevity is not nearly as important as being clear and easy to understand.

A good explanation includes the problem, the solution and the criteria of success. This explanation is both general and specific, addressing both the problems our new technology is solving and why.

The tl;dr

I learned a lot of communication tips while at Google, and one of them was the importance of tl;dr — an acronym for “too long; didn’t read.” While I’d seen this on Hacker News and Reddit for years, I’d never used it in my work communications. When you’re dealing in hundreds or thousands of emails a day, a one or two sentence overview to determine the importance of a larger block of information is incredibly valuable. When used correctly, a well-crafted tl;dr can save people from distractions and time lost in topics that they either don’t need to know or already understand.

The key here is to summarize the problem, solution and ask in as few words as possible. If you’re writing more than 2 sentences, you need to cut it down. If you can’t then you need to go back and look at the point of your email itself, it may be too broad. The tl;dr is for your organizational “power users” who can’t spend their time reading every word of every email.

The Subject Line

This is where we find our ability to generate consistency and the urgency of communication. While it’s tempting to use the tl;dr in the subject, this prevents our ability to create a predictable pattern. There are 2 main types of emails subject lines I write: ACTION REQUIRED or ATTENTION REQUIRED. Make it as clear as possible from a subject line if you need the recipient to take action or read the email.

If your subject line doesn’t include a message that basically says “HEY! I NEED YOU TO DO THIS,” then expect it to be ignored or opened when the recipient is cleaning up their inbox. Obviously this won’t be true of every recipient, there are no guarantees, but you can try your best by specifically calling out that you NEED them to pay attention or take action.

The Recipients

The two worst mistakes you can make with comms is sending it to an unnecessarily large group and sending it to an unnecessarily limited group. There is a lot of nuance to finding that happy middle ground and much of that changes from one organization to another. For me it’s normally something I find by trial and error.

Generally, you can start by addressing the folks you are making the ask of, their direct manager or management group and the core leadership. Depending on the org, some leaders love seeing this and the visibility is normally good for you as a sender. However, you may also be quickly asked to stop spamming people if the messages are too frequent. Start with a larger group than you think, and whittle down from there — it’s much easier to apologize and adjust from a large group to a smaller one than to have to recover from appearing to silo your comms.

Example & Template

Attached is the working example, Sample of an Effective Organizational Email in addition to an easy to use Template for an Effective Organizational Email.

Read more from Max here: https://medium.com/@maxisnow

Writing an Effective Organizational Email was originally published in LIFION by ADP on Medium, where people are continuing the conversation by highlighting and responding to this story.