Consulting
Operations Excellence | Part 2
Welcome to the “Operations Excellence” series! As we interview our company personnel, we delve into all things Operations at Orange Bees — from maintaining a healthy work culture to making sure our clients are happy, and everything in between.
In our second article of the Operations Excellence series, Phil Hunt (Chief Architect), Lee Garkusha (UI/UX Design Lead), and Stephanie Travis (Engineering Agile Master) discuss their take on the “consultant mindset,” their personal consulting experiences, and best practices.
Tina: To start us off, can you all explain what it means to be a consultant?
Lee: To me, being a consultant means utilizing your expertise to help someone solve a problem.
Phil: I agree. Not all roles within a company are going to be software and technology experts. As a consultant, we’re brought in for our expertise. The biggest reason companies hire us consultants is because we’re supposed to know what we’re dealing with and how to solve the specific problem at hand, whether it’s industry knowledge, technical knowledge, or previous experience.
Stephanie: Being a consultant also means you can enter a situation without a clouded perception of constraints that may have existed in the past for the client. You’re able to think more abstractly and provide some solutions that they maybe hadn’t thought of before.
It is about helping the client figure out what they actually want and/or need. A constant challenge with any kind of consulting is how to navigate steering your client in the right direction. With the exploratory phase of a project, we are given the opportunity to meet with clients and figure out exactly what they want and how we can implement that for them.
Tina: Great, so as a consultant, what are some of the challenges you tend to run into?
Phil: There are tons of challenges because you are expected to know a lot. You may go to a prospective customer and you’re just not a good fit. Not necessarily you personally, but the company in general. Sometimes you will be asked to do something that is outside of your company’s scope. Another challenge is that a lot of people don’t have ‘people-skills’ and have a hard time working with customers. Some people over-promise things — it’s a tradeoff between wanting to impress the customer early on with your knowledge and ideas, while not overselling what you can do as an individual or a company. These are all challenges that consultants face, and it’s a fine line trying to find the right mix.
Lee: Along those lines is being able to talk to a lot of different people. When you’re working within your own company, you get used to working with certain people and you learn their personality and their styles. However, when you’re consulting, you’re constantly talking to new people, so you have to learn how to best work with certain clients. Some people may be more available to work with, some may be more opinionated than others — you must learn how to work with different personalities, which can be a challenge.
Phil: Absolutely. Sometimes, it’s even the terminology — figuring out what the customer is really asking when they can’t put into words what they’re trying to say. They could say something, and you’ll think they meant one thing but in reality, they meant something totally different. I’m not referring to just language barriers — it’s understanding that when someone says something, we need to dig deeper to figure out what they really mean.
Stephanie: It is about helping the client figure out what they want versus what they’re telling you because often they don’t actually know what they want until you’ve made something they don’t like. I think that’s a constant challenge with any kind of consulting: how do you navigate steering your client in the right direction early on to do that exploratory phase, which in turn, helps make sure that you understand what they need.
Phil: Especially with UI and UX, the customer already has an idea in their mind of what the product is going to look like and how it’s going to flow, and so when they come in and you show them something different, a lot of the time their first thought is, “That’s not what I was expecting.”
Some of that is working with them to help us figure out what the problem is instead of telling us the solution they have in mind. Sometimes the customer’s solution is the only solution. We have to combine our expertise with the customers to come up with the best way to solve their problem.
Tina: Are there certain tools that you use to help explain or layout your plan in the initial meetings with a client, specifically on the UI/UX design side?
Lee: I take a lot of notes at the beginning and then I use a lot of mapping and diagramming to organize my thoughts, such as information architecture maps, which would show the navigation of the existing application, or simply grouping the data model, just so I can get that in my head and visualize the notes that I have. A lot of times, that’s what I’ll use at the beginning before I even start sketching.
Phil: One challenge we find in this phase is, if we’ve already given a statement of work and we start going through ideas, sometimes it just grows in scope. The designers aren’t doing anything wrong, it’s more that we’re expecting this to be a simple, little screen, so when we get asked, “Can we add this, this, and this? Can we add, undo, and redo?” These are good ideas, but we have to get the customer to understand that the price is already set so we can’t give you every cool feature you come up with after the scope of work has been agreed on.
Stephanie: To that point, as consultants, part of our job is to help guide the clients to what is going to give them the most value. The 80/20 rule comes into play here: what is the 20% we can do to give them 80% more value?
Also, we often must steer them away from adding all those other little things that might be helpful to one or two users, but do not really add a ton of value at the end of the day. This is often a challenge.
Phil: Yeah, we are better off focusing on MVP and go wide, and then go back and go deep on the parts after they use it. Then, they can say, “Okay, this could be easier if we had these two extra features.”
Most of the time, the customer is going to get really excited about the cool, little visual things like “undo” and “redo.” It sounds neat, where you can just go edit, hit control Z, and undo things, but that’s a lot of effort development-wise and then you end up spending all your time on those things and you’re not really focusing on the actual business problem.
Tina: That makes sense. Can you explain how consulting overlaps with Architecture and/or Design? What role does an Architect or Designer play in consulting?
Phil: The consulting pieces come into play the most upfront in projects and less and less as time goes on because by then there are more professional services implementation.
Consulting is 100% about architecture and design upfront. As a matter of fact, we sell customers on the idea that we’ll do the upfront architecture, the UI/UX design, etc., and if you want to, you can take this to somebody else and they can implement it. It’s not a bluff but they never do because by then, they’re usually pretty comfortable with us. The consulting piece can always be taken elsewhere to be implemented if the customer finds a cheaper option, but that inherent knowledge is the hardest part to transfer from one person to another. If Lee worked on the UI/UX design for three months and you bring in somebody else to implement it, with no ability to reach out to Lee anymore, it can be really hard for another company.
Stephanie: I would say, in both Phil’s and Lee’s positions, they really are set up to be the initial advisor to the client and help them on the path forward. Everyone in our company should be thinking like a consultant, but in an architecture and design role, you really set the path for the rest of the team, which is critical.
Tina: Going off of this, how does being a consultant play into professional services?
Phil: The biggest thing is that all engagements start with a consultation on the consultant side. Then, that works into the professional services, which usually goes into a statement of work or a rough order of magnitude — some idea of cost. We then work with the customer, get paid, and start doing more of the professional services, which is where we take our ideas and get them implemented. The consultants are usually still around after all this, just in a lesser role.
Get Orange Bees’s stories in your inbox
Join Medium for free to get updates from this writer.
Lee: Or sometimes the consultant is the one that actually implements it. In my case, I’m usually still going to be the one who does the design, mockups and wireframes, and things like that, after I’ve asked all the questions in the beginning. Sometimes, depending on capacity, we may have to switch it up and Erin (UI/UX Designer) might have to take over, but I think we have good processes and documentation so it’s really easy for one of us to pick up the other’s projects, as needed. For the most part, we try to keep the same person on a project, so no one has to relearn anything.
Stephanie: Going back to the point of adding value, you can go to a lot of professional services companies, and they’ll give you a list of their services and rates. Consulting goes beyond that. Going back to the earlier idea around advising, consultants help to work outside of the box and create solutions that are appropriate for the unique challenges of individual businesses.
Phil: Even the way we do professional services is more on the consulting side because we’ll do the project management, Scrum master, project execution, and documentation. Often times, professional services require three Java Developers and a SQL Server DBA for six months at a certain rate. While we do a little bit of that, most of what we do is project work, which is more on the consulting side of things.
Tina: Okay, so what are some common mistakes or pitfalls to avoid as a consultant?
Lee: Making or accepting assumptions is a common mistake that consultants tend to make. Going back to what Stephanie said earlier, it is important to make sure you’re asking enough questions and the right questions. Especially when the client comes to you with what they think is the solution, consultants shouldn’t accept that but rather take it with a grain of salt. What the client offers could end up being part of the solution or even the full solution, but it could also end up being completely different. If you just take what they say as assumptions and truths, you may end up building something that they don’t really need.
Tina: Yeah, at the end of the day, you are the consultants so you need to determine what is best for your client, rather than the other way around.
Phil: Part of the reason you hired us is that we have the experience and knowledge. However, consultants need to be mindful of arrogance or coming across with arrogance. We still have to be empathetic towards a client’s ideas because a lot of the time, they aren’t using the right terminology or have a hard time relaying their idea, but they do have a great idea. They know what they want, they just don’t know how to put it into words. We as consultants should not dismiss their ideas until we’ve explored what they’re trying to say.
Stephanie: Another pitfall is considering constraints to be a negative. Oftentimes constraints actually create an opportunity for further creativity, leading to an unexpected or more innovative solution.
Phil: Also, making sure that you’re not spending too much time on “exciters” and spending more time on the features that make the system useful. I used to work with a project manager, one of my favorite people to work with, and we were working on a project together and the customer would come up with an idea that was out of our scope, so he would say, “but let’s talk about what you really want.” We would still talk through it, and he would give them an estimate for it, but he would explain that it’s out of our scope. He was just really good about listening to what the client had to say. Through experience, you see all these different business processes and through each one you learn something that worked well and something that didn’t.
Stephanie: I think that’s one of the biggest benefits of bringing a consultant in — they’re bringing expert knowledge to the table, not just from your industry but from various industries.
Tina: These are some great insights you all are offering.
We briefly discussed this earlier from the UI/UX side, but how do you approach solving a client’s business problems? Do you visualize things mentally, or do you use certain tools and applications?
Lee: Yeah, so as I mentioned earlier, on the design side, I use diagrams and sketch things out, which really helps the client visualize the product. I usually don’t show them my information architecture diagrams, unless they ask for it. Once I get into sketching, wireframes, and user flows, that’s when I’ll start showing them what I’ve created to help them visualize it as well.
Phil: On the software architecture side, you model everything. You model their business processes, their domain, and what properties you need. You model how the different software components fit together. You start with a very high-level abstraction, like 100,000-foot view, then you go to the 10,000-foot view, and eventually the 1,000-foot view, and somewhere in there you build the code.
Working with the customer also helps because they’ll point out relationships and things that they understand. If you do all this early enough, you can fix it with an eraser in an hour, but if you wait six months into the project, there’s no longer an eraser. You’ve got a bunch of code that’s written and now it’s very expensive. You’re trying to avoid rework and for me, the act of modeling helps me get my own thoughts straight.
Tina: That’s great! I just a few more questions, so moving right along: how do you recommend steering clients towards what is best for them? Is there a certain approach you’ve found that works the best?
Stephanie: I think step one is simply being an active listener. Giving clients that courtesy and respect upfront helps to establish a level of trust and respect. You sometimes have to establish that relationship before offering a solution that will be accepted.
Phil: Yeah, it’s a much easier time, and a true back and forth, when you’ve got a relationship with your customers. They trust you and you trust them. You do have to recognize that sometimes there will be a certain hot button for them, and they aren’t going to budge from their decision, and you just have to deal with it.
Lee: Yeah, but you wouldn’t be doing your due diligence if you didn’t tell them all the pitfalls, so if you can think ahead and tell them why this might not be the best solution, they might understand. Like Phil said before, if it ends up deprioritizing a feature that is more important, then they’re probably not going to end up picking that solution.
Also, instead of just convincing them of your ideas, you should communicate in a certain way that makes it feel like you’re arriving at a solution together, or even that they are the ones coming up with the solution on their own. This way it doesn’t feel like you’re trying to influence them in any way. People are more likely to be excited about something that they come up with.
Stephanie: One way of guiding people is by asking great questions. That’s something I know that Lee and Erin do very well. They think through questions that the client may not have thought important, which really helps guide the client to decisions.
Tina: Does knowing what is driving their needs, such as pressure from investors or upper management, play a role in steering client’s decisions?
Phil: That always affects the client’s decision because there’s multiple different triangles in this industry. You can make the product fast, good, or cheap, but you can’t do all three. It’s knowing what’s more important to the client. They may want simple and quick and want to go back later to make it look good, but right now, the focus is on making it simple and quickly. Knowing the driver really affects what the product will end up looking like.
Tina: Alright, do we have any last tips or thoughts about consulting?
Phil: I will say this: there is a different set of skills one must acquire when working on the consulting professional services side, as opposed to working for a product company. A lot of times when we are hiring people that have never done professional services, it’s very eye-opening for them because you work with a lot of different people. You may be working on one project and with one set of customers for months, and once the project is done, you might be working with a totally different company or industry.
When you work for an internal software development staff, you may be doing something in finance or manufacturing, so it’s a different skillset. It’s not better or worse, it may be just that they’re not really suited for it. When we’re hiring people one of our biggest issues is that they’ve never done professional services consulting. We always try to make sure they understand that this is going to be a different pace than what you’re used to.
We try to keep it so that most of our mid-level and senior people are only working on a couple of things at a time — 80% on one thing and 20% on something else. When you’re used to working in a product company and you come to consulting professional services, there’s a whole lot more going on.
Lee: Yeah, I agree with that.
Stephanie: Yes, and I would just add that critical thinking plays a large role in our jobs as consultants and wraps up a lot of the things we have already spoken about. As a consultant, you have to think critically at every turn about how your decision today is going to affect the customer going forward.
Tina: That makes a lot of sense. I know I’m definitely learning a lot from you all, so thank you for sitting down with me to speak about your experience in consulting!
Be sure to follow us on LinkedIn & Facebook to keep up with the latest Orange Bees news and updates, and the release of the next article in this series!
Thank you to M. Judson Booksellers for allowing us to use their space. This aesthetically-pleasing bookstore is located in the beautiful Downtown Greenville and is a great work and hangout location. Don’t forget to grab a sweet treat at the bakery inside!









