Chapter 21: New Challenges

Chapter 21: New Challenges


Three weeks into working with my new team, I'm discovering that managing employees involves challenges I never anticipated during my years as a solo practitioner. It's Tuesday morning, and I'm sitting in my office trying to mediate a disagreement between Emma and Sofia about client filing systems while simultaneously reviewing Marcus's proposal for reorganizing our project management processes.

"Grace," Emma says, her usually cheerful demeanor strained, "I think we should organize client files alphabetically within each service category. It's more intuitive for scheduling appointments and retrieving information quickly."

"But Emma," Sofia counters, "organizing files by priority level and project complexity makes more sense for workflow management. It allows us to batch similar types of work and allocate resources more efficiently."

Both approaches have merit, which makes this exactly the kind of management decision I'm not equipped to handle. In Chicago, someone else made these decisions. Here, they're looking to me for leadership I'm not sure I can provide.

"Let me think about this," I say, buying myself time to figure out a solution that works for both of them. "In the meantime, can we use Emma's system for active client files and Sofia's system for project planning?"

The compromise satisfies neither of them completely, but it allows us to move forward while I figure out a better long-term solution.

After Emma and Sofia return to their respective tasks, I open Marcus's proposal for implementing project management software. His recommendations are thorough and professional, but they would require training time, software costs, and a significant change in how we handle client work.

My phone rings, interrupting my review of Marcus's proposal. It's Harold Miller, and he sounds frustrated.

"Grace, I tried to call yesterday to schedule an appointment, but I got a message saying you were fully booked for the next two weeks. Is that right?"

"I'm afraid so, Harold. We're managing more client projects than I anticipated, and I want to make sure everyone gets the attention they deserve."

"I understand that, but Grace, we have a time-sensitive situation with our conservation program documentation. If we don't submit the paperwork by the end of the month, we could lose our subsidy eligibility."

The urgency in Harold's voice reminds me that rapid business growth creates problems for clients as well as employees. People who used to call and get immediate appointments now have to wait weeks for consultation time.

"Harold, let me see what I can do. Can you bring your documentation by this afternoon? I might be able to review it between appointments."

"That would be a huge help. Thank you, Grace."

After we hang up, I realize that I'm facing a fundamental business management challenge. My team is working efficiently, but we're still not keeping pace with client demand. I need to either limit new client intake or find ways to serve existing clients more efficiently.

The problem is compounded by the fact that I'm spending increasing amounts of time managing employees rather than serving clients directly. Training Emma on client communication protocols, reviewing Sofia's analytical work, coordinating Marcus's system improvement projects—all of these activities are necessary, but they reduce the time I have available for the hands-on consulting work I love.

Emma knocks on my office door. "Grace, do you have a few minutes? I need to discuss something with you."

"Of course. Come in."

Emma sits down in my consultation area, and I can see that she's choosing her words carefully.

"Grace, I love working here, and I think we're building something really special. But I'm struggling with some aspects of the job."

"What kind of struggles?"

"Time management, mostly. Clients call expecting immediate answers to complex questions, but I don't have the technical knowledge to provide them. So I have to interrupt you or Sofia, which disrupts your work flow." Emma's voice becomes more frustrated. "Yesterday, Mrs. Patterson called asking about depreciation schedules for her floral equipment, and I had no idea how to help her."

"What did you do?"

"I asked her to hold while I found Sofia, but Sofia was on a call with another client. So Mrs. Patterson had to wait ten minutes, then call back later when Sofia was available."

The situation illustrates a problem I hadn't fully considered. Emma has customer service skills and administrative capabilities, but she lacks the technical knowledge to handle many client inquiries independently.

"Emma, what would help you feel more confident handling client questions?"

"Training, probably. If I understood the basics of tax planning, business accounting, and financial analysis, I could handle routine inquiries without interrupting you or Sofia for every question."

"Would you be interested in taking some continuing education courses? Accounting fundamentals, small business finance, tax preparation?"

Emma's face lights up. "Absolutely. Grace, I want to be as helpful as possible to our clients, but I need more knowledge to do that effectively."

"Let me research some options. In the meantime, let's create a resource guide you can use for common client questions."

After Emma leaves, I add "employee training program" to my growing list of management responsibilities. It's becoming clear that running a successful team-based practice requires skills I don't currently possess.

Sofia knocks on my door an hour later, also looking like she needs to discuss something important.

"Grace, do you have time to talk about workflow challenges?"

"Always."

"I'm concerned about our project management. We have excellent individual capabilities, but we're not coordinating effectively as a team." Sofia pulls out a handwritten chart. "Look at this week's schedule. Emma scheduled three client consultations during the same time slot when I planned to work on the Henderson ranch analysis. Marcus is reorganizing the filing system while I need access to historical client data for the Johnson business review."

The chart makes our coordination problems visually obvious. We're working hard individually, but we're not working efficiently as a team.

"What do you recommend?"

"We need systematic project management. Regular team meetings, shared calendars, clear communication protocols, defined roles and responsibilities." Sofia's voice becomes more enthusiastic. "Grace, Marcus's software recommendations could solve a lot of these problems, but we need to implement them systematically."

"What would that involve?"

"Training time, initially. Maybe a full day for system setup and team training, then follow-up sessions to address problems and optimize our processes."

"How much productivity would we lose during the training period?"

"Short-term, maybe twenty percent. Long-term, we could probably increase our efficiency by thirty or forty percent."

The trade-off makes sense, but it would require closing the practice for a day and rescheduling client appointments—exactly the kind of disruption I want to avoid.

My phone rings again. This time it's Jake, calling during his lunch break.

"How's the team management going?" he asks.

"It's going. Jake, I think I may have underestimated the complexity of running a multi-person business."

"What kind of complexity?"

"Everything from filing system disputes to training needs to project coordination challenges. I feel like I'm spending more time managing employees than serving clients."

"That's normal for a growing business, Grace. Management responsibilities increase with staff size."

"But I didn't become an accountant to manage people. I became an accountant to analyze financial data and solve complex problems."

"What if you approached employee management like a complex problem that needs analyzing and solving?"

Jake's suggestion reframes my management challenges in terms I understand better. Instead of seeing employee issues as distractions from my real work, I can see them as analytical problems that require systematic solutions.

"You know what? That's exactly the right way to think about it."

"What would your first step be?"

"The same as with any complex problem—gather data, identify patterns, develop systematic solutions, implement changes, and measure results."

"That sounds like a solid approach."

After talking with Jake, I spend the rest of the afternoon analyzing my management challenges systematically. I create charts showing time allocation, workflow patterns, communication bottlenecks, and training needs.

By the end of the day, I have a clearer picture of what's working well and what needs improvement. Emma is excellent with clients but needs technical training. Sofia is analytically strong but needs better project coordination tools. Marcus's organizational recommendations could solve several efficiency problems but require implementation time.

The solution becomes obvious: I need to invest in systematic team development the same way I invested in business development when I first started the practice.

I schedule a team meeting for the following Monday to discuss our coordination challenges and plan solutions. I research continuing education options for Emma, review Marcus's software recommendations in detail, and develop a timeline for implementing Sofia's workflow management suggestions.

Most importantly, I remind myself that building a successful team-based practice is just another complex problem that requires the same analytical approach I use for financial consulting—careful analysis, systematic planning, and measured implementation.