ArrowLinkToArchivePageBlog

A complete guide to organizational structure of Predica Team roles and goals

Predica started back in 2009, and since then a lot has changed in terms of how we operate, deliver, and achieve our goals. And also (not surprisingly) in terms of our size – as of 2022, we have over 400 people on board.

We are not a massive organization, but we needed to develop a well-defined structure to manage every unit seamlessly, determine the direction of our operational activities, chain of command, and flow of information.

In this article, you will find out how we are structured right now and what are the key roles in our organization (spoiler alert – it’s not the C-level!).

Key points

  • How are we structured as an organization?
  • What are the two most important roles that drive our business?

Who we are, what we do, and how we do it

Let’s start with a brief explanation of what it really means to be a Microsoft technology consulting company.

#1 Our focus

We focus on Microsoft technology, and specifically its 3 clouds: Azure, Microsoft 365, Dynamics 365. In Dynamics 365 we address the CRM segment: sales & customer service. We do not cover ERP: finance & operations. For Azure and Microsoft 365, we cover the entire breadth of the Microsoft portfolio.

#2 Our approach

We are consultants at heart. This means we put the clients at the center of everything we do. We aim first to deeply understand their context, limitations, and challenges. Only then do we determine if (and how) the Microsoft cloud can help in their specific situation.

So, it does happen that we redirect our potential clients to another company or technology. We may also propose a cheap & fast method to determine fit (like Proof of Concept) if we are not sure whether the platform can help them. We don’t sell our specific products but have worked out a number of useful patterns, frameworks, or ready-to-use offerings that address some common challenges we see across multiple organizations.

#3 What we do 

We are technology consultants. We focus on how technology can help or transform the business. But we are not business advisors, nor do we help with process re-engineering.

We work with companies in multiple sectors, and they understand their industries much better than we ever could. Our goal is to assist them in understanding and implementing modern technology to supercharge their business.

Sounds simple, right? Not when over the last 13 years we grew as much as we did. We needed to organize ourselves into functions, teams, and roles to deliver on our promise of  reliable services on the Microsoft cloud.

The organizational structure of Predica

Here you can take a look at the overall organizational structure:

Overall company structure

Overall company structure

Any bigger organization needs to develop departments or functions to allow each group to focus on the specifics. It is of utmost importance to not create silos out of these teams. We aim to work with the client perspective always at the front of mind and cooperate on our goals.

To clarify the company structure, here is a visual summary:

Predica team structure

Predica team structure

Key roles at Predica

A while back I wrote two articles detailing two key roles in Predica:

And even though we grew almost 3 times, since the first article was published, they are  STILL THE MOST IMPORTANT ROLES  at Predica. Not the CEO, COO, CFO, or CTO – no! The most important roles are the ones that sit at the intersection of direct client contact and technology.

These 55+ individuals  (as of October 2022 but more are still coming!) are the bedrock of Predica. They define what we do with our clients, the details of our promise to them – and that’s a huge responsibility.  But ‘it takes a village’ to deliver this promise and that’s where the rest of the firm steps in.

Project Owner is a project-specific role, while Digital Advisor is an organizational role and job title in our consulting team. Digital Advisors can be thus Project Owners on one or multiple projects.

Enjoying your read? Leave your email address to get the latest industry updates delivered to your inbox every two weeks. Subscribe

Predica leadership team

As for company leadership, we practice and preach a self-managed culture. This means that everyone is encouraged to take ownership of specific areas, projects, clients, and make their dent in the universe.

The reporting structure at Predica exists for only 2 reasons:

  • Servant leadership: the leader acts to remove obstacles and helps pave the path to success for their Team Members
  • Mentoring: the leader is not a manager, directing orders, but a friend who inspires Team Members and helps achieve their goals.

The current leadership team structure looks as below, but  as a company growing 30-40% YoY, we undergo changes at least every 9-12 months.

We are excited to continue 2022 with such a strong management team. But the truth is that every single person in the company contributes to fulfilling our mission – to help people focus on more meaningful work. Without our amazing team of Predicans, none of our goals would be achievable.

If you’d like to join us on this journey and get involved with our mission, check out our current opportunities (there are plenty of them!)

Key takeaways
  1. Our teams are meant to fulfill three specific functions – Engagement Success, Client Success, and Practices. They all have their own goals and missions, which sum up to the overall purpose of Predica – deliver reliable services on the Microsoft cloud.
  2. The two key business roles at Predica are Digital Advisors (our consultants) and Project Owners (we use this term instead of Project Managers, which really changes the approach to everyday work!). Both of these roles require direct contact with the customer, and that’s what makes them so important. 

Sign up for Predica Newsletter

A weekly, ad-free newsletter that helps cutomer stay in the know. Take a look.

SHARE

Want more updates like this? Join thousands of specialists who already follow our newsletter.

Stay up to date with the latest cloud insights from our CTO