Video: Firms Underestimate Time Commitment in Software Implementation | Summary: Stress the underestimated time commitment firms must invest during software implementation and training
Video: Effective Change Management and Post-Launch Success Strategies | Summary: Effective change management ensures team alignment and gradual adoption of new systems for long-term success.
Video: The Importance of Reverse Demo in Software Selection | Summary: Highlight the importance of reverse demos to analyze current workflows before implementation begins
Video: Switch Systems Without Surprises: Prepare Your Firm for a New Practice Management Platform | Duration: 1908s | Summary: Switch Systems Without Surprises: Prepare Your Firm for a New Practice Management Platform | Chapters: Welcome and Introductions (5.98s), Session Overview (116.405s), Pre-Implementation Assessment (308.92s), Data Evaluation (497.015s), Change Management (614.785s), Change Management Strategy (817.82s), Weighing Feature Trade-offs (1051.725s), Questioning Must-Haves (1400.84s), Change Management Strategy (1563.88s), Implementation Timeline (1694.58s)
Transcript for "Switch Systems Without Surprises: Prepare Your Firm for a New Practice Management Platform":
Hello, everyone, and welcome to today's session, switching systems without surprises. A few housekeeping items before we dive in. The session is being recorded and you'll receive the recording after the session concludes. So, with that, I will just dive into some introductions. I am happy to be here today with my co presenter, Nancy, from thirty five forty five. Nancy, do you wanna go ahead and, give us a quick introduction? Sure. Thank you, Jen. Nancy Griffin, founding partner of thirty five forty five Consulting. We are, strong advocates of action step, and so I'm excited to be able to present this with you today. I've been working in the industry for over thirty years and have had lots of experience on doing... Choosing software, selecting software, implementing software. So it'll be nice to have a discussion with you, Jen, and share some of that information with our audience. Absolutely. Alright. So, my name is Jennifer Ramos. I'm the vice president of global solutions here at Actionstep. But prior to joining Actionstep just under three years ago, I graduated from law school in 2001. So I've walked in a lot of your shoes. And then I spent about nineteen years doing what Nancy does, and that is helping law firms pick their practice management, time billing and accounting, document management systems, really working through process analysis and understanding what the functional requirements would be, for a law firm. So Nancy and I both have, a lot of great stories to tell as far as being in the trenches and helping firms with software selection. But not only selection, but also what makes it... What do we need you to do? What do we need to do to be prepared to implement a new a new product? So I am excited to get started. And before we get started, we'll talk a little bit about what we're gonna cover today. We're gonna check the linen closet, and that will make more sense here in a minute when I tell you guys a quick story. And then we're gonna talk about the work you need to do before go live. What happens when you move into the new house, weighing the scales, and then we'll do a little bit of q and a. So, to set the stage, just a little anecdote for you all. My husband and I, my family moved from Ohio to Chicago, several years ago. And I went to Chicago for a weekend in the suburbs, and I looked at 27 houses in the course of two days. And so that was a lot of houses, often, like, you might look at a lot of different pieces of software. And, we bought a house. And when I moved into the house, I started unpacking and I went to put away all my sheets and my towels and I realized that there was no linen closet. And I really didn't understand how this could happen. Right? I'm... Here I am with boxes full of of of linens, and I have nowhere to put them. And I started to think to myself, how did I not know there wasn't a linen closet? And I started to think, whose fault is it that I don't know that there's a linen closet? Should I have known... As the buyer, should I have made sure there was a linen closet? As the seller, should they have disclosed that there wasn't a linen closet? Should my realtor, as the consultant, have said, hey. Do you want a linen closet? Where where where did that ball get dropped? And it really made me think about what happens often with software selection, and that is we make some assumptions, right, because we're human and we often make assumptions that the things we're used to, I've never lived in a house without a linen closet, that the things that we're used to will be there. It's not unreasonable to make assumptions. But this happens with software all the time and we assume that the features we have in our current systems exist in every program, so we don't always ask about it. But you really do need to. So I probably should have said to my realtor, I I can't have a house without a linen closet. But at some point, we we have to take our assumptions out of the equation, and we have to think about every single thing that we do, even the things that we take for granted. And we need to make sure that the next piece of software will either have the feature or will have an equivalent way to accomplish the goal, the thing that you were trying to accomplish. Right? Turns out I had plenty of space in my bathrooms and my kids kept their sheets in their bedroom... In their bedrooms, and it worked out. It was a working solution. It wasn't a deal breaker, but it did shock me. And what we wanna try to do in today's session is help you avoid the shock, avoid the landmines, and really be prepared to pick the right piece of software and then have a successful implementation. So think about the things that you do every day and automation that you rely upon, a report you run every week, and make sure that you talk to the team that's involved in in picking software. The risk isn't the missing feature. It's just that nobody got to ask or talk about. So that's gonna just set us up a little bit for, the work that we need to do before go live. And Nancy's gonna lead us through a number of items here, about things that we really feel you should be focused on before you make your decision and before you go live. So, Nancy? Sure. Thank you, Jen. Yes. It's really important to understand what you're currently doing in your application. It... It's wrote memory to all of you because you're doing it on a day to day basis, But this is the time to really pause and not only look at what you're currently doing, but what you want to do in your next software choice. So what's working, what isn't working? By mapping through the workflow, understanding what you're gonna do or what you're doing by role, by area of practice, by lawyer, then you have a much better chance of being able to truly understand what you wanna do in the new software. So the concept here is to give everyone a voice. That voice will carry you through to the new software program. If we leave anybody out of the process, then when we get to the new house, we may not have exactly what we need when we get there. So very important. Looking at the templates and making sure that you understand what templates you're currently using and what you need to be able to use is so critically important. A lot of times, we assume that everything that we're currently doing is a necessary part of what we should be doing, and that may or may not be true. Templates are a great example. What do you need to have and how do those particular templates and forms need to work in the new system? Process documentation. This is something that very few firms in all the years that I've been in the industry coming across somebody who actually has standard operating procedures documented fully and completely is a rarity. But now is the time to actually do that and to say, let's figure out exactly what it is that we are doing so no assumptions are made when we're making the selection of the new software. And then data cleanup could not be more important. Making sure that duplicate contacts are removed, making sure that unbilled work in progress from the billing and accounting perspective is handled, deactivating matters so that we don't have everything as an active matter. Those are some of the things that can be done as a preliminary process and can certainly make a migration go much more smoothly. And then I can't emphasize enough the importance of doing a reverse demo. So once you get into the actual selection process, it's really important to show what you're currently doing in your workflow process. As implementers, we really strive to have that reverse demo done again before implementation begins so that we can understand truly what it is that you're doing on a day to day basis. And then reporting. Reporting runs the world, and it is very common for law firms to think that the most critical reports that they use and live by on a day to day basis exist, that there is a linen closet in the next product. And in fact, there may be or it may be that the reports are a little bit different in the new system. So understanding what reporting you're using and taking a good evaluation to say, is... Are these reports really what we need to be evaluating the firm on on a go forward basis? So that data conversion, active versus inactive data, looking at your custom data, understanding the limitations, of course, making... Not making assumptions, and seeing what is a value, what you need to be able to see in the new system. So that... This is where we take that secondary step. Evaluate what you have, and then evaluate what you need. Those are two very different things, and being able to take the two and separate them will give you a much stronger implementation. The other thing is to search and look for all those hidden spreadsheets that you have all throughout your system, whether they're from a practice management perspective or whether they're from a time billing and accounting perspective. Those spreadsheets can more than likely be automated or become a part of your standard workflow if they're exposed early on. And then it's so critically important to embrace change management. Jen and I had a great discussion about change management and really how to approach it with your firm. And I think, Jen, you were you were very adamant as we had our our discussion about how important change management is and how to overcome their... The fears. Yep. Yep. You know, Nancy, I'm sure you've experienced this as well. But when when you engage with a law firm, you... You're often working with a kind of a smaller group of people that might be the product champions or the committee that chose the software, and, you become... You get pretty close with them. You start to learn you start to. learn a lot about the way the firm works, about personalities in the firm, what have you. But one of the things that I think is really important is that as as the consultants or... And even as the vendor that the the firm feels like they have an advocate in you and that you are trying to make sure that they're making the right choice. And, you know, we... One of the things that Nancy mentioned at the be... At at the beginning of these slides was, like, include everyone. Right? Don't exclude everyone. We appreciate that if you're in a 50, 75, 100 user firm, you're not going to involve a 100 people in the decision. But you have to involve a 100 people in the in the knowledge that a decision is being made. And it's really important for them to know that you're looking. Know that there is change coming. Gather feedback about what they like and dislike about the program. Learn what they use the product for in their current job. Learn about their fears. What are they worried most about when we change software? And then one of the number one things that I think firms miss when they are planning a new software implementation is that oftentimes they they they partner up with a great partner like thirty five forty five and they they receive their their quote for the work and there's a lot of time involved on the on the consultant side, but the firm fails to recognize the time commitment and the expectation from their perspective. So we're gonna we're gonna document workflow and process. Guess what? That's gonna take time. You're going to need to do that. You're gonna need to share that with your consultant, with the vendor. Those things take time. We're gonna review that process. We're gonna do a build out in the new system. We're gonna do user acceptance training, and then we're gonna do go live training. And and those are time commitments that the firm is often underestimating, and then they're surprised and they get sometimes frustrated or they feel stressed because they don't feel like they have the right amount of time. So I think it's really important to, to share with the with the team members at the firm. Listen, you're maybe going to need to commit one or two hours a week for the next three months on this project and make sure that leadership supports the commitment of that time and that we're not asking support teams, paralegals, associates to work more hours in order to be a part of the software selection. It's just so critical. When you have people that wanna be involved, don't have the time to be involved, or don't have the support from leadership to be involved, it's really not a a great recipe. So I do feel really, really strongly about the change management part. And I think it also lends itself to the fact that when you have that support and when you have that interaction and when people are truly engaged, then when the software goes live, they have a personal investment in it, and they. feel like they're a part of it. So it isn't something that's being imposed on them. It's something. that they're a part of, and they're growing with the firm together. That's right. That's right. So growing with the firm together, it's like moving into the new house together. So just a couple of quick slides here to talk about, you know, that move. So, yes, it it is, very important in order to be able to think about your change to a new software program as being a move to a new house. My analogy is when you move into a new house, if you take all of the broken furniture and parts and pieces that aren't going to fit in the new house, then it's just not gonna be a good move. So it's time to be able to segregate those things that you don't wanna bring into the new house and then to rearrange things so that it fits within the new house, and it really looks attractive. And maybe buy some new things along the way in order to make the house look more attractive. That's taking advantage of those new features that you're purchasing and making sure that they're incorporated. It's a sad day when a law firm will come to us, and they've been using a product for a year, and they will say, we know we haven't even touched or scratched the surface of all the features in the product itself. That's heartbreaking because you were so excited about it to buy it from the very beginning. You wanna stay excited about it when you move into that new house and make sure that that experience is great. And explore every nook and cranny and hope there's a linen closet along the way too. That's right. You know, one of the things we also try to avoid, Nancy, is showing up on training day and having someone say, I didn't know my job was changing today. And this really ties back the importance of that change management and the importance of getting everybody involved from the beginning. I can remember on more than one occasion when when we used to sort of leave the change management up to the firm and as consultants, we didn't wanna we didn't wanna tell the firm how to communicate. We really got to a point where when I was a consultant where we we talked about the need for it because it it just really was ending up... You know, you'd show up on go live day and you're the trainer and all of a sudden, 20 people in the conference room really don't like you because they had no idea what was happening today. Right? And and I've just decided I didn't wanna I didn't wanna be in that position anymore. I've had people in the first day of training say, I have a question. I manage all the medical records, and I had a list in insert old system name here, that I... That was automatically emailed to me every week, and it tracked the date I made the request and how many days they had to send it and what I needed to follow-up on. How will I do that in this system? And I'm sitting there going, I don't know. Nobody told me that you were gonna need to do that. Right? It goes back to we didn't ask everybody. We didn't include enough people. We didn't give everybody a voice as Nancy mentioned. It doesn't mean that when you pick software, you'd go to a 100 people and say, what do you need it to do? And then you find the piece of software that does the 400 things that those... That combined that those people needed to do. Right? But you have to know what you need to accommodate for. And it's not just about asking what feature did you use and what feature do you need. It's what what goal are you trying to accomplish that you use this feature for, and how can we accomplish that goal in the new in the new system? The biggest fear that people have is, how am I gonna do my job in this new system? Because you didn't change my billable requirement. You didn't change my workload. Now I have to learn I have to learn how to do it. It's just like moving into a new house. Right? I still have plates and glasses and silverware, but they're all in a different place. And I'm weeks and and months sometimes remembering where things are. This is about preparing your team so that they never show up on training day and realize the whole... Everything they knew about how to get their job done was changing. The. other thing we wanna talk about... Yeah. The other thing we wanna talk about is kind of weighing the scales, and Nancy does a great job with this. It's like you you are going to potentially lose a feature that you liked in your old system, but we have to weigh that against what we gained. So, Nancy, I'll let you talk about that for a little bit. Yes. Definitely, when you see a new software program and you get excited about the new features that are there, then we definitely can say at that point in time, oh my gosh. We're gonna gain efficiency by by doing, AI timekeeping. We're going to be much more efficient by being able to have our lists and being able to look at our lists and evaluate contacts that are in our system as an example. Well, those exciting features, once you really get into the drudgery of the change and you start to see what you may be missing can be forgotten. Because sometimes we can't just exactly have the same thing in the new program. As an example, I had a client that was absolutely adamant that a particular budget report just had to be in their new system, and they actually turned turned down the software program because it didn't have that budget report in there. That's a sad way of doing it in spite of the fact that they saw all these great features in the new program. Well, sometimes that same feeling occurs when we're doing implementation. We look at a slight difference in our workflow or a different way that we have to work, or maybe we have to find where the dishes are in which cabinet. And so that throws us off a bit, and we start to forget all of the great features that we have in the program. Maybe one thing is a little bit less efficient than what we did before, but maybe 10 things are more efficient than what we did before. And sometimes it's hard in order to. see kind of the big picture of how everybody feels. In that one example, I was very sad for the firm because one person's time commitment of maybe a couple hours a month to generate this specific report was going to prohibit the firm from appreciating all the value of the wonderful things that were there. So when you're going through implementation, it's important to recognize maybe a particular individual or a work group has an extra step or two involved in a workflow process. But you must always balance that with all of the advantages and those things that you are really going to capitalize on from those strong features of practice management or time billing and accounting. That's right. So we'd really love for any of you who are joining today that are really on the the precipice of of of selecting new software, really think about the things that you expect to gain and and and take this with you to every demo that you do. Like, when you when you are looking at software, what was presented to you that feels like a gain? And weigh that against anything that you might be losing. And compare the list, right, which which side is heavier? We understand that sometimes there is a particular thing that's a deal breaker. Right? But it's really important to identify those things that are really going to make an impact on the firm and make sure you're making decisions based on the greater good and not necessarily, like Nancy said, the the two hours from one person who... While we appreciate that that's frustrating, it's sort of it's sort of time to take one for the team. Right? So when you when you look at the things that you expect to gain and the things that you are worried about losing, we also want you to really build your requirements. So I always call these functional requirements, and sometimes they would be these big long lists on a spreadsheet of of the feature and then a column for whether each of the products I was demoing had the feature or not, and then a place for notes as far as, like, anecdotes about the feature. Look at slide one. Right? What were your workflows that you documented? What were your processes that you documented? Think about what you do now and and start writing down what your functional requirements are so that you can analyze that list against the different demos that you get. I want to encourage people not to completely use a generic checklist of what functional requirements should be. And and and you might be as surprised as me that it's, you know, twenty twenty six and neither... Nancy and I have only said AI once as she would refer to AI timekeeping because that's the buzzword, right, that everybody's talking about. I have been on more calls in the last two years where someone asked an agent to give it a checklist of things they should care about when picking a practice management program. And use that as a start, but please look at that list and and make sure it is tailored to your firm. I had a call just a few months ago after one of our one of our account executives sent me a a a spreadsheet that had over 200 items of functional requirements on it. And they wanted me to go through and say yes, no with customization, you know, give them an idea of whether or not our particular product could could meet those needs. And over a 100 of them, I had questions about because we word things differently, you you make an assumption about something that you shouldn't have, and it was just really hard to know what they were asking in these in these quick little sentences in one cell on a spreadsheet. So we set up a meeting. It was four different people from Actionstep and it was six people from the law firm. And we went through my questions. And out of the close to a 100 questions I had, over 80% of their answers were, you know, I don't even know what that means. I don't know how that one got on there. And it... Come to find out, they had generated it from Claude, and it... They hadn't really read it before they sent it to us to say, does that make sense? Does that something we need? Does that... Do we do we care about that? And so, you know, my guess is of those five people on the call, two or three of them were billable, and that was just a... An opportunity for them to to waste billable time, and we really accomplished nothing other than they realized, you know what? We can't use a generic list. We need to understand our own processes and what we're looking for so that we can really understand what is a must have and what is just something that we're familiar with and and and we're not really we're not really bothered by. So when we talk about functional requirements and you talk about the things that are must haves, nice to haves, whatever, I want you to always be able to explain the why behind the must have. Why must you have it? Let's talk about a report. Nancy referred to a report. Maybe there's a report that you must have, and you think you must have it because when you started, someone taught you how to run it, and that report goes to a partner every Friday, and that... That's a must have. We have to have that report. Have we ever asked the partner, do you still review that report? What action do you take based on that report? Would you be willing to get that report, emailed to you, or would you be willing to look at that report in a dashboard that you can access that maybe doesn't require a human to cobble it together manually? Oftentimes, the the things we are... We can... We consider to be a must have are really just habits we were never in a position to question. And a lot of times, the the heavy lifting, the work gets done by our support teams, and they might not feel empowered to question it or say, I have a better idea, or is is there any way we could try to streamline this so it doesn't take me three hours to put this report together? Especially if you're someone who goes into the office and sees the stack of reports every week and they don't look like they've been touched. Right? Don't be afraid in your law firm, whatever your role is, don't be afraid to ask why. And it doesn't have to be because you're being critical and you're trying to be a problem. You're just someone who is is embracing the the opportunity, as Nancy pointed out at the beginning, to to leave bad workflows and bad processes behind. Don't carry those into to your new system. We we talked about this actually earlier when Nancy mentioned it and I and I jumped in about change management. But one of the things that I used to do as a consultant, even though I didn't ask a 100 people to join all the demos, I did ask firms if I could send every user a short survey. Very short basic questions like, what do you like about the current software? What do you dislike about the current software? And what scares you the most about switching software? And number three can really be telling. We did this survey once when we were, we had a firm that had an established financial program and an established document management program, and we were simply adding practice management. And there was a paralegal who answered question three paragraph after paragraph. I I probably should have put a character limitation on it. Paragraphs of her fear and frustration and frankly anger about them switching document management systems and how they they just figured out how to save huge volumes of medical records and it's working and the team knows it and she can't believe they're gonna... We weren't changing their document management program. We were only adding practice management and it was gonna integrate with their document management program. What that did to me is it made me realize there has been no change management. That was an extreme example, but what these questions can also provide for you is there are things that people like. Have we accommodated for those things, in the new software? Have we overcome the things that they dislike about their current software? Is it is it gonna be better in the new software? And have we have we addressed the fears about what it's gonna be like to get their jobs done? And sometimes those surveys, which you can, you know, you you can pop into quad and it could help you summarize them. You didn't have to get a 100 people on a demo and get too many cooks in the kitchen, but you at least gave everybody an opportunity to share some of their concerns and things about, the way that they get their job done. So, talk talk to your, talk to your firms about change management, and and I'll let Nancy kind of wrap us up here with a little bit of the firm wide communication plan. Yes. So definitely, the... Before you go live, you wanna make sure that everybody understands what you're doing, why you're doing it, and they're all bought in to the fact that this new change is gonna be very beneficial for the firm. During the go live, it is critically important that everybody finds out what is it that they're supposed to be doing today, and what will they be doing tomorrow. How do they get to that point and feel fully trained and full fully ready to embrace the new software. But don't forget the after go live. Again, we don't wanna end up a year later saying, we know we're not using all the features of the software. We wanna be able to say, as of the go live, we're gonna be using the features that are critically important, and we can't absorb all the great features of these new programs. We just can't absorb it all in one sitting. But we're gonna commit to using those features over the next twelve months so that at the end of that twelve month period of time, we're saying we are using all of them, and we understand the benefits and the the practical application of those features to our firm in particular. Wonderful. Well, thank you, Nancy. That brings us right to our time. But I will check the q and a. I don't think I see any questions in there. But one of the things that people often ask, and I'll just add it as a as a parting thought here, No. The the timelines for implementations like this is often a very common question. You know? How long how long will it take? And I like to just kinda set people's expectations that it really varies by firm, but you should you should, sorry, I got distracted by the... By my other screen for a second. You should be spending a decent amount of time investigating software. If you think you're going to look in November and go live on January 1, that's not a reasonable expectation. It can take months sometimes even just to get your workflow and your process documented to a point... Documented to a point where you can build a functional requirements document, and then you're managing the calendars of the team that's gonna pick the software and the vendor and the consultant. So give yourself the right amount of time even to just pick the software. And then the timeline for implementation is often more about the client's availability than anything else. Right? Do they have the time to give? Do they have the time to meet with the consultants? Are we... Do we have the time, a block of time that doesn't cross over into vacations of critical people, etcetera. So it's it's hard to give a a timeline other than to say whatever you think it is, it's probably more and to make sure that you give yourself the gift of time when making a decision this big about the product you will use to run your entire business. So thanks for... Everybody. Thank you, Nancy, for, for your time and your expertise. And as I mentioned at the beginning, we... You will get an email with a link to the recording. And if you want to in... Want to learn anything more about Action Step practice management, we would certainly love to chat with you, and you can book a demo on our website at actionstep.com. Thanks, everybody.