The B2B Podcast Index
Index
All categories
MarketingSalesSaaSFinanceHROpsLeadershipCustomer SuccessAI & DataProductStartups & FoundersRevOpsEngineering & DevTools
MethodologySubmit
Best of:MarketingSalesSaaSFinanceHROpsLeadershipCustomer SuccessAI & DataProductStartups & FoundersRevOpsEngineering & DevTools
An independent project byFame
SearchBest episodesGuestsInsightsMethodologySubmit a podcast
Index/AI & Data/Tech-Driven Business
Tech-Driven Business artwork

Inside Insights: Leading Project Teams to Success with Anuya Sheorey

Tech-Driven Business · 2025-05-12 · 18 min

0:00--:--

Anuya Sheorey, a leader at Nikola Automotive, presents a practical framework for bridging the persistent gap between strategic planning and operational execution that plagues scaling organizations. As Nikola transitioned from an agile startup to a rapidly scaling manufacturer, Sheorey realized that traditional project-based structures couldn't maintain alignment across business and IT functions. Her solution: adopting a product-centric, value-stream-based model borrowed from manufacturing and Lean Six Sigma methodologies. Rather than organizing around company divisions, Nikola created 11-12 cross-functional product teams aligned to customer journeys - the truck journey (manufacturing), customer journey (sales and service), and energy journey (hydrogen dispensing). Each team maintains a backlog, has a business owner as product owner, and operates under enterprise governance that communicates high-level strategy while allowing teams autonomy in execution. This structure eliminates the traditional "business versus IT" friction by making them part of a unified value stream team. She also discusses how Nikola leveraged SAP as an operational backbone while implementing broader data and analytics strategies to democratize access across peripheral systems like CRM and manufacturing platforms. Sheorey's key insight: transformation success depends on people - their involvement in decision-making, their sense of ownership (the IKEA effect), and continuous learning cultures that keep teams adaptive in a rapidly changing landscape.

Key takeaways

  • →Shift from project-centric to product-centric, value-stream-based organizational structures to eliminate business-IT silos and maintain alignment as organizations scale.
  • →Define value streams around customer journeys and business outcomes rather than internal departmental boundaries to create truly cross-functional, self-organizing teams with clear ownership.
  • →Implement governance frameworks that communicate enterprise strategy from the top while allowing product teams autonomy in prioritizing their backlogs and execution decisions based on value stream contribution.
  • →Data and analytics strategies must balance centralizing core operational data in systems like SAP while ensuring peripheral systems and data sources are accessible and don't require constant manual reconciliation when core systems change.
  • →Transformation success is fundamentally about people - their involvement in problem identification, inclusion in decision-making, and intrinsic motivation to embrace change - not about technology implementation.

Guests

Anuya Sheorey

Topics in this episode

Customer journey mappingGovernance frameworksLean Six SigmaValue stream mappingCross-functional teamsManufacturing operationsData DemocratizationProduct-centric organizational structureSAP S4 ERP systemsNikola Automotive

Questions this episode answers

How do you align business and IT teams when they have conflicting priorities in a scaling organization?

Sheorey recommends eliminating the distinction between business and IT by creating unified value-stream teams organized around customer journeys or business processes rather than departments. The product owner from the business side prioritizes the backlog based on enterprise goals communicated by governance, while IT delivers on those prioritized items as part of the same team.

What is a value stream and how do you apply it outside of manufacturing?

A value stream is a sequence of activities needed to respond to a customer need or deliver value. At Nikola, they defined three: the truck journey (design to factory floor), customer journey (initial contact to service), and energy journey (hydrogen dispensing). Each becomes the organizing principle for a cross-functional product team spanning IT, operations, finance, and other disciplines.

How do you handle cross-functional initiatives that span multiple value streams and create overlap or friction?

Enterprise-level goals communicated through a governance committee provide the constraint and alignment mechanism. Product teams prioritize work based on how their value stream contributes to those enterprise goals, which ensures teams work in the same direction even when initiatives overlap across value streams.

What data and analytics strategy works when you have both a core ERP system like SAP and multiple peripheral systems?

Sheorey recommends using SAP as the backbone for operational data while implementing a broader analytics strategy that democratizes access to data across all systems without requiring constant manual updates when the core system changes. This allows business teams to analyze collective organizational data rather than isolated system views.

How do you stay current with rapid technological change like AI?

Sheorey practices continuous learning through reading, podcasts, newsletters from thought leaders, and deliberately taking on assignments outside her expertise. She extends this to her teams by regularly asking what they learned and encouraging a culture where daily learning is expected both at work and home.

Conversation analysis

Computed from the transcript - who did the talking, and the words that came up most.

Share of words spoken

  • Speaker B61%
  • Speaker A39%

Most-used words

value18teams13product11stream11strategy9framework8journey8different8transformation8team7sure7organization7streams7customer7technology7data7

Episode notes

Ever wonder how to truly get business and IT on the same page, moving beyond strategy documents to real project success? In this latest episode, Anuya Sheorey of Nikola Automotive joins Mustansir Saifuddin to dive into how to lead teams across diverse landscapes, focusing on how to bridge that critical gap between high-level goals and daily execution. Anuya shares firsthand experiences and the framework used to align everyone from the C-suite to the front lines. It's more about the people than the technology. Anuya Sheorey is the Head of Program Strategy & Enterprise Solutions at Nikola where she leads high performing teams to enable rapid scale-up through ongoing delivery of critical capabilities across manufacturing, operations, finance, sales and service. As a strategic technology leader, she is passionate about connecting business strategy with technology execution and has a proven track record in orchestrating enterprise-wide digital transformations in diverse industries such as insurance, transportation, electronics and utilities to drive growth and operational excellence.

Full transcript

18 min

Transcribed and scored by The B2B Podcast Index.

Speaker A: Welcome to Tech Driven Business brought to you by Innovative Solution Partners. I'm honored to have Anuya Shoroi of Nikola Automotive join me to discuss how she leads teams across diverse landscapes, focusing on how to bridge that critical gap between high level goals and daily execution. Listen in as Anuya shares a framework she uses to align everyone from the C suite to the front lines. Welcome to Tech Driven Business. Anuya, how are you?

Speaker B: I'm doing great. Mr. Very good to see you.

Speaker A: Thank you. I'm so excited to have you on our show. We'll be focusing on uh, or talking about leading teams and working across business and IT landscapes. And I know that's your sweet spot, that's your area of expertise and how this all relates to of project success. I would like to discuss your real life examples. Good to get some insights into that.

Speaker B: Absolutely. Glad to be here and talk with you about my experiences. Will be wonderful. Thanks Mustan Siva.

Speaker A: All right. I think one of the things that I always like to start with is your experiences. Based on your experience, you've seen a lot. It can be very challenging to get business and IT folks really on the same page. Right. Especially your C level strategy team, how you align them with the folks who are actually doing the work. What are some of the ways you have been able to break through those silos and bring those projects to fruition?

Speaker B: Yeah. So as a company and when we were smaller, Nicola was smaller, we were very agile and nimble. Right. It was very easy for us to just have a strategy in place and make sure that those strategies are executed. As we started down the path of scaling, uh, rapidly, it was important for us to make sure that we maintain that nimbleness. But at the same time we wanted to make sure that we were able to bridge that gap between strategy and execution that you just spoke about. Right. How do we make sure that there is end to end ownership and improved line of sight for the enterprise goals? Right. The project was successful. How do we make sure that it's moving the needle in terms of what the organization is trying to achieve now do we have buying from cross functional teams? Are they prioritizing the work? All of them working in the same direction and drawing in the same direction, if you will. And so the other thing to that to add is also are we focusing on the outcomes as opposed to individual tasks? Oftentimes teams get so focused on individual tasks and individual KPIs. So just to give you a soccer analogy, for example, are we measuring how many times the ball was passed or are we measuring how many goals were made? You know, so all of that has to come together really nicely as well. And so to help with solving some of these challenges, we decided to shift our operating model from a project to a product centric framework. Now this is used often in software product companies, right? But how do we use that kind of a framework in a company like Nikola was the challenge that we kind of were working through. And so we created these self organizing, cross functional teams that were perpetual, constantly working on business outcomes and continuous improvements. And so the way we defined these product teams were in terms of value streams. Now some of your listeners may be familiar with this value stream kind of a UH framework which is used in manufacturing and Lean Sigma kind of a UH model. And the way we define value streams for the purpose of our product stream was a sequence of activities that were, that are needed to be taken to respond to a customer need or to deliver value to the customer. And so in our case we defined three distinct journeys. We defined a truck journey, a uh, customer journey, and an energy journey. Because Nikola is the truck manufacturing company and also we dispense hydrogen, we are an energy company as well. If you look at the truck journey, what are some of the operational processes needed to support manufacturing of drugs? So right from designing a truck to when it rolls off the factory floor, that's the truck journey. Similarly we identified right from the initial contact to the customer to when we service the customer, that's the customer journey. And similarly for hydrogen dispensing capabilities, we identified the inner. So we created 11, 12, I am going to say different product value stream kind of teams that spanned across the enterprise. And we had an owner from the business, it was staffed with SMEs who were actually cross functional. So it was not bound by organizational structure or divisions within the company, but it was defined by the value stream really. And of course it as well. Then this team was responsible for maintaining a backlog of items and improvements that they worked on. Whether it was training needed, whether it's an uh, enhancement from an IT perspective needed, or just ways of working that needed to be improved to continue to work on the improvements in value UH stream. So that was kind of the framework that we used to bridge that gap between strategy and execution and the role that the governance. So we had a governance committee that worked along with these different value stream enterprise wide. They were responsible for communicating the strategy. Where do we want to see the organization go? And these product value streams then decided how do these, their value streams contribute towards that enterprise Goal. So that's kind of the bridge between the enterprise goal, the goals of the value streams. And so the product owner then was really the voice of the customer or the subject matter expert that decided what needed to be done to achieve those metrics. And then the IT team took that on and decided how to deliver.

Speaker A: I think you mentioned a couple of very good points. I like to focus on, um, the cross functional teams. And based on some of the experiences I'd had, I know cross functional teams is a great way to get things done because now we have knowledge base from all the different parts of the organization. But how do you keep that balance between who makes the call and how this call is executed across the business and IT teams? Because you may have, sometimes the business may take a lot more focus or their focus can be, um, a bit different than a technology perspective or it may have a different view on that. Did you run into any of those challenges during your journey?

Speaker B: So I think the beauty of this whole framework was that there is no longer business and it here. Right. It's uh, a value stream team. So it's a team that is working on challenges to make the value stream more effective. So they would map out the as is business process for that value stream and said, okay, what are some ways to improve things here? Then that really drove the backlog for the team. And I think the product owners were responsible. The one person responsible for prioritizing this is the thing that we will focus on. But then what drove the constraints for how they would prioritize was the goals that came from the enterprise. Right. Why should we be doing this? Came from the governance committee. And so that helped align the different teams as well. Because oftentimes we also had initiatives that span beyond a value stream, not just one value stream. So how do you make sure that you are aligning all the different value streams to work and draw in the same direction? That was the goals framework that helped with that.

Speaker A: Yeah, absolutely. And I was about to go to that point that, you know, your value streams can crisscross and when you have those overlaps is where the friction comes into play. And how do you manage all those, all those challenges? Right. So great, great answer. Kind of leads me into my next task over here. More than often you find yourself as part of their decision making process. Data and analytics is front and center of this because that's what allows you to make those decisions based on the information you have available. What are some of the top factors that stick out for you? When you look at having an SAP S4 system and wanting to do analytics and reporting solution for your organization. What is your take on it?

Speaker B: Yeah, at cola, initially our priority was just enabling the core functionality that would help with the rapid scale up and transformation of the business. So we quickly realized that if we had to grow as an organization, we needed a more robust data and analytics strategy in place as well. And so while SAP was our backbone for operational data, uh, finance, manufacturing, inventory, we did have peripheral systems and sources of data as well. And I think that's what got us talking to Mustan. Sir, when we initially met is how do we go about doing this? You were a great partner and we talked about.

Speaker A: Thank you.

Speaker B: How have you seen this playthrough? Several options we were considering at that time. How do we make sure that we are able to democratize access to the data and at the same time ensure that we are not constantly having to touch it every time we change something in SAP because that's not the easiest thing to do. And so that's kind of what our thinking for deciding which solution to go forward with and what should be our strategy long term from that point on.

Speaker A: Yeah, I think that's a great view of that situation because I remember when we had that discussion and I find myself a lot of times in those conversations where you have your backbone system, SAP or any other ERP systems for that matter, but you also got to have other peripheral systems from CRM to any other manufacturing system, et cetera, in your landscape. And the goal or the challenge usually for business is I'm looking at the overall organizational data and I want to do some analytics on top of that. Not my financial system or my supply chain system alone. It's a mix of information that I'm looking at. So it feels like you were able to look at a collective data set and then make those decisions. Absolutely, that makes sense. And that's good because uh, based on your experience, I know you worked in a variety of industries and technologies. How have you been successful leveraging third party resources to support your teams? What is the formula that you use?

Speaker B: Yes, unfortunately it's not a uh, formula, but it's more a partnership. I've worked in diverse industries. Insurance, transportation, electronics, utilities. One of the key differentiating factors for extended partner relationships that have uh, worked for me in the past have been the ones where companies have stepped up to co create the innovative solutions with us. They are able to bring in best practices to the table guide discussions, make themselves trusted advisors in the process. These are the companies that have imported true partnerships for us. And we've built long term relationships with some of these companies.

Speaker A: I think they're super interesting. You use the word partnership more often. It gets overlooked when you are working with customers. A lot of times the conversation comes up as the SI is doing the implementation or an outside third party is being brought in to help us with this technology transformation. But the concept of partnership kind of sets aside that whole idea of a third party working as a team, trying to create something. And you saw that partnership successful based on your past experiences.

Speaker B: Yes. And I have seen that is the only kind of relationships that have been successful. Because oftentimes if you think about companies as sis, there is a lot of things that get lost in the translation. There is handoff and a lot of communication challenges that come to it. Whereas if they are involved from the beginning, they are true partners in the success of the initiative. That makes it a successful partnership and a program. And it's a win win for Holtz. Really?

Speaker A: Absolutely. I think the end of the day it's not about the technology, it's about the, uh, actual business, uh, benefit of it. And the way you described the relationship, I think is what really comes out as a finished product at the end of the day. Right. From the business perspective. So I know we've been talking about technology and business and all that. We all know we are living in this AI world. Everything is moving super fast. The world is changing by day, by hour. How do you stay on top of everything that's going on?

Speaker B: I love doing it. That's why. So I am an avid learner. I'm um, a continuous learner and a reader as well. So I tend to take up assignments that I know nothing about with the objective of learning because that drives me personally. I'm always on the lookout for classes, reading, whether it's books or podcasts or blog posts, newsletters of some leaders, thought leaders that I follow. And so that's kind of what I do for my teams. I have followed a similar thing that I've been asking them questions. What did you learn today? Do that even at home, whether we have that conversation, you know, TABLE what did you learn today? Whether it's from your day to day work or whether you read something interesting. Interesting. And I think that's kind of what helps me stay up to date as well.

Speaker A: Uh, do you think that, that, that learning is allowing you to get to your next level faster than you anticipated? Or have you seen that, that drive in learning helping you move forward?

Speaker B: I would link. I would like to think so. But I think it also helps me do a better job at whatever role that I'm operating in or whatever task that I'm undertaking as well. Because I have heard perspectives of other people who've gone through similar things, learned from their lessons. I, um, have a wider pool of mentors to draw from from that perspective as well.

Speaker A: It always helps to have a mentor. Right. So that, that's one thing that you can always appreciate when you're going through your journey. I know we talked about a lot of different things today as we coming to the end of our session. I, uh, like to have one key takeaway that you want to leave our listeners with today.

Speaker B: Yeah. So as we think about how to bridge the gap between strategy and execution, which is kind of been the theme of this podcast here, the way I look at it is any transformation effort at the end of the day is all about people. You need inputs from them. They are closest to the work being performed. You need collaboration and buy in cross functionally across the organization for people who are going to execute on some of those strategies. And you need them motivated and ready to embrace the change that goes along with any transformation effort. As we saw in the example of the product framework, uh, what that did was it empowered people to take on some of the work, to take on some of those challenges. And it had a two pronged benefit as well. They were the ones identifying the changes that were needed. And also since they were involved in the decision making process, it's kind of the IKEA effect, right? People, if they're involved in making a product, they have pride in it. And that is easy as buy in from those people as well. And so any transformation is less about technology, it's more about people.

Speaker A: I like it. I think I don't often hear this thing and um, this idea about, it's always about transformation. And everybody's excited about the transformation and the technology and of course it's exciting, but we tend to leave the people part out or minimize that. But I think, uh, what I'm hearing from you is you keep the people up front and center, then everything around it kind of blends in or kind of smoothly moves forward.

Speaker B: Absolutely.

Speaker A: Well, thank you so much for joining me today. I would love to continue the conversation, but we got to come to our end, so thank you so much.

Speaker B: Thank you. Mustan M. Um, sir, glad to be here.

Speaker A: Thank you for listening to Tech Driven Business brought to you by Innovative Solution Partners. Breaking silos and bridging strategy and execution can be challenging for any organization. Anuya's um, key takeaway. Any transformation is less about technology and is more about people. We would love to hear from you. Continue the conversation by connecting with me on LinkedIn or X. Learn more about Innovative Solution Partners, and schedule a free consultation by visiting isolutionpartners.com Never miss a podcast by subscribing to our YouTube channel. Information is in the show. Notes.

Related episodes across the Index

Other episodes covering the same guests and topics, from across The B2B Podcast Index.

  • The Toyota Method That Could Transform Dentistry. Why AI Multiplies Mess Without ItThe TechDental Podcast · on Lean Six Sigma95 / 100
  • Increasing messaging power with customer-centric branding.Real B2B Brands · on Customer journey mapping91 / 100
  • Inside Microsoft-scale sales operations with Chinesh GandhiThe Sales Compensation Show · on Value stream mapping86 / 100
  • How B2B Marketers Use Customer Marketing for ExpansionB2B Marketing with Fexingo · on Customer journey mapping83 / 100
  • Digital CX with Real Impact: Kat Kenny on DAP, AI, and Customer Education | Episode 108The Digital CX Podcast · on Customer journey mapping80 / 100
  • B2B Marketing Metrics and KPIs: insights from experts at Sage, Sun Life and VitalPathB2B Marketing Leaders Podcast · on Customer journey mapping80 / 100

More from Tech-Driven Business

All episodes →
  • Inside Insights: How AI is Disrupting Traditional Consulting Models with Shashank Paritala58 / 100
  • Inside Insights: SAP's Enterprise-First Approach to AI with Andrea Haupfear
  • Inside Insights: SAP Business Data Cloud (BDC) Adoption Roadmap with Shawn Brown
  • Inside Insights: Business Case for SAP Business Data Cloud (SAP BDC) with Shawn Brown
  • Inside Insights: The Evolving Landscape of SAP and Agentic AI with Geoff Scott
Explore the best B2B AI & Data podcasts →
All Tech-Driven Business episodes →