Zach shares his story, starting from his days at the Arkansas Coding Academy to overseeing technology and innovation at Metova. Learn about his current role, the challenges he faced, and the passion for learning that continues to drive his success.

📌 Episode Highlights:

- Zach's responsibilities at Metova, including project sizing and scoping

- His early interest in technology and the pivotal moment that led him to the Arkansas Coding Academy

- Key lessons and the impact of the Academy on his career

- The journey from student to VP, including the importance of soft skills and client communication

Follow us on LinkedIn to stay updated with the latest from Metova. Thank you for tuning in, and special thanks to Zach for sharing his journey with us. See you in the next episode!

• Host: Alondra Cruz
• Guests: Jonathan Sasse & Andrew Cowart
• Duration: 14 minutes, 54 seconds
• Release Date: 1/8/2024

Overview:

In this episode of "Software Savvy: Tech Talk for non-tech people," we explore the dynamic world of technology, strategy, and innovation with a focus on Metova's Strategy Sprint Sessions. Host Alondra Cruz sits down with Jonathan Sasse, Chief Strategy Officer, and Andrew Cowart, Chief Technology Officer, to unpack the intricacies of Metova's unique approach to strategy and tech reviews.

Key Highlights:

1. Introduction to Metova's Strategy Sprint Sessions

• Alondra introduces the episode's theme: the significance of strategy and tech reviews in today's fast-paced digital environment.
• Emphasis on the expertise of Jonathan Sasse and Andrew Cowart as key players in the tech strategy game.

2. Insights into Strategy Reviews (00:02:34)

• Jonathan provides a detailed overview of the strategy review process.
• Discussion on the key questions, focus areas, and the creation of a comprehensive scorecard.
• How strategy reviews help businesses understand their strengths, weaknesses, and opportunities.

3.Tech Reviews Unveiled (00:04:19)

• Andrew delves into the tech review process, distinguishing it from longer assessments.
• Exploration of the two segments: current technology ecosystem and future technology roadmap.
• The role of tech reviews in bridging the gap between the present and desired technological transformation.

4.Preparing for the Sessions (00:05:19)

• Insightful advice from Jonathan and Andrew on how businesses can best prepare for the strategy and tech review sessions.
• Emphasis on having core stakeholders available and bringing forward current challenges and concerns.

5. Complementary Roles of Strategy and Tech Assessments (00:07:02)

• Discussion on how strategy and tech assessments complement each other in a full engagement.
• Jonathan and Andrew provide insights into their distinct perspectives, focusing on "who and what" and "how and when."

6.Post-Review Process and Reports (00:09:29)

• Jonathan and Andrew share what businesses can expect post-review, including customized reports.
• Discussion on how these reports serve as catalysts for informed decision-making and strategic planning.

Closing Thoughts:

• Jonathan emphasizes the importance of approaching the sessions with an open mind, comparing it to a therapeutic conversation.
• Andrew emphasizes that Metova's role is to provide a sounding board, not replace existing teams.

Next Steps:

• Alondra announces the landing page for booking one-hour strategy or tech review sessions with Jonathan or Andrew.
• Limited spaces are available, encouraging listeners to sign up on the Metova website.

Schedule a Session today! https://metova.com/strategysession/

Outro:

• Follow Metova on LinkedIn for updates.
• Subscribe to "Software Savvy" on preferred podcast platforms.

Evaluate where you are starting. Are you starting from zero or have you already accomplished a certain amount of work in trying to define what your product is? What have you already created,  produced, or defined - anything you can share to help create some kind of a scoping reference for the team you’ll be working with. Can someone else start to understand your idea and your vision?

Some questions to consider…

1. Who is this product for? 
2. What problems does it solve? 
3. What are the business objectives? 
4. Who are the people that are gonna be using it?
5. How are they gonna be using it? 

Understanding Project Ranges

A product of any kind, from a web, mobile, or custom software perspective, could have a wide range of costs. The more you invest in defining what your scope needs to be and who it's for, the more you can leverage a budget that will work for your project.  

The House Analogy

You wouldn't ask somebody how much a house costs without giving them some idea - where is it? How big is the lot? How many square feet is it? Otherwise, you could be talking anywhere from a hundred thousand dollars to tens of millions of dollars. The same goes with software. You’ll want to be as transparent as possible in the beginning, in order to be able to produce the results that you want and that are within your budget. 

Is there room to grow after you set your scope?

• This is where we lean on the strategy team with our clients to see where they are at. What is their particular industry vertical like? What is their niche like? What makes the most sense when it comes to developing software?
• Do we take a very bare-bones, MVP approach that might be a bit more cost-effective and agile to develop? Or is this a critical, "it has to be right on the first go", release? 
• A lot of these things get easier to figure out the closer to the deadline you get because requirements change, constraints change. It's easy to sit down and whiteboard- plan all of it out and then once you get into the reality of the situation, you might realize you need to pivot some, and all of this is happening while the market's ever-shifting.

Knowing when to sit in your project’s definition

Understand that you could work on the definition forever. Look at what the objective is. Are we trying to get something to market as soon as possible at the highest quality possible with a minimum feature set? There's a goal that needs to be met there. A lot of times, things can get a little sideways when the ideation phase of the project never really stops.

• You want to get, where you know what your core personas are, you know what they need, you know what problems you're trying to solve and you have an idea of what your go-to-market plan is. Even if go-to-market is an internal review of some sort, you satisfied the definition to the point where you can meet that milestone.
•  If there are timeline or budget constraints that are driving the project, ensure that the entire team has to be aware of those constraints and know when those trade-offs need to be made. 

Don’t be afraid of an MVP!!

Rapid prototype style development is one of the best happy mediums if you're caught somewhere between, "I have all these great ideas and I've thought it all the way through, but I've not really started yet." Take pieces that are much more budget-friendly and just build out units of that. While doing that, do it in a paint-by-number way where we know where all the numbers are, but we're just going to paint in the certain things that we're able to, and bootstrap an app that way. Break it down...]]>How to start scoping?

Evaluate where you are starting. Are you starting from zero or have you already accomplished a certain amount of work in trying to define what your product is? What have you already created,  produced, or defined - anything you can share to help create some kind of a scoping reference for the team you’ll be working with. Can someone else start to understand your idea and your vision?

Some questions to consider…

1. Who is this product for? 
2. What problems does it solve? 
3. What are the business objectives? 
4. Who are the people that are gonna be using it?
5. How are they gonna be using it? 

Understanding Project Ranges

A product of any kind, from a web, mobile, or custom software perspective, could have a wide range of costs. The more you invest in defining what your scope needs to be and who it's for, the more you can leverage a budget that will work for your project.  

The House Analogy

You wouldn't ask somebody how much a house costs without giving them some idea - where is it? How big is the lot? How many square feet is it? Otherwise, you could be talking anywhere from a hundred thousand dollars to tens of millions of dollars. The same goes with software. You’ll want to be as transparent as possible in the beginning, in order to be able to produce the results that you want and that are within your budget. 

Is there room to grow after you set your scope?

• This is where we lean on the strategy team with our clients to see where they are at. What is their particular industry vertical like? What is their niche like? What makes the most sense when it comes to developing software?
• Do we take a very bare-bones, MVP approach that might be a bit more cost-effective and agile to develop? Or is this a critical, "it has to be right on the first go", release? 
• A lot of these things get easier to figure out the closer to the deadline you get because requirements change, constraints change. It's easy to sit down and whiteboard- plan all of it out and then once you get into the reality of the situation, you might realize you need to pivot some, and all of this is happening while the market's ever-shifting.

Knowing when to sit in your project’s definition

Understand that you could work on the definition forever. Look at what the objective is. Are we trying to get something to market as soon as possible at the highest quality possible with a minimum feature set? There's a goal that needs to be met there. A lot of times, things can get a little sideways when the ideation phase of the project never really stops.

• You want to get, where you know what your core personas are, you know what they need, you know what problems you're trying to solve and you have an idea of what your go-to-market plan is. Even if go-to-market is an internal review of some sort, you satisfied the definition to the point where you can meet that milestone.
•  If there are timeline or budget constraints that are driving the project, ensure that the entire team has to be aware of those constraints and know when those trade-offs need to be made. 

Don’t be afraid of an MVP!!

Rapid prototype style development is one of the best happy mediums if you're caught somewhere between, "I have all these great ideas and I've thought it all the way through, but I've not really started yet." Take pieces that are much more budget-friendly and just build out units of that. While doing that, do it in a paint-by-number way where we know where all the numbers are, but we're just going to paint in the certain things that we're able to, and bootstrap an app that way. Break it down to components where you can answer “If nothing else besides this MVP is built, will this still work?” Prioritize the components that do work, because those are going to be much more budget-friendly to get out there and see working.

What should we consider technically?

What platforms do you want to be on? (by platforms, we mean the web, android applications, iOS applications, etc..). 

• The more places you are, the more expensive it is. If you want to make an offering in all of those different markets, there's a barrier to entry for each of those regulated markets. App stores are a lot more guarded and require a lot more care than it would take to just build a website. 

How many people do you intend to use this application? Where are they?

• You can make a website that's hosted off of a laptop in a closet in your office, and that can be your server. And if you're only using it within the office, you might be able to get away with it. But, If you want to provide something on demand across the globe, we're talking about using advanced cloud architectures that are able to run things. So this is one of those cost sliders where we always ask:

1. Who's the target audience here? 
2. Where are they geographically?
3.  How many people are you trying to target?  
4. How long are they gonna engage with it?

What work does the software do?

On a spectrum of complexity, on the light side of this is Content Delivery software (like Twitter) where users are consuming the information. Sometimes they're providing information and consuming information. As we move into more complex software, the delivery of those includes more calculating and automating features, which can do a lot.

• (For Example) If you go to any big box store, all of their inventory systems are terminals. They don't need to be very super user-friendly because the stores train their people to use the systems. But if you're trying to provide a powerful application to novice users who may not be trained, then it takes a lot more work to prepare for all of the different circumstances and give a human the ability to influence the software in a way to attain an outcome that they would anticipate.

Don't get caught up on specific vendors or the cloud architecture setup you go with.

• A lot of that is secondary to exactly what it is you're building and the complexity:

1. Where you want this available?
2. How often do you want it available?
3. What kind of uptime do you want?
4. What does the software actually do at the end of the day? 

Plan ahead!!

If you think that there's a shadow of a possibility that you're going to want a dedicated Android or iOS app, establishing that up front will be key.  

• The cost associated with switching platforms is something that a lot of people may not understand. If you have a budget constraint, it is often good to use a hybrid platform, which is essentially a coding platform where we can build your application in such a way that it can be deployed to the web, iOS, Android, or any mobile app really, from the get-go. It may cost a bit more than the option of solely creating the website, however, it will save money in the long run if you decide to create an offering on a mobile platform.   

Understand that it's pretty rare to build a software product and then just finish building. 

• You will have to budget for product updates and maintenance going forward. Sometimes, that can be a surprise for people; they think they're going to take possession of their software on some particular date and it's just gonna work in perpetuity for all of their customers. In most cases, that's pretty rare.

Questions to ask tech agencies

1. what is my monthly cost going to look like?
2. Does my product scale?
3. Does it scale with the number of users I serve? 
4. Does it scale with time? 

Be transparent about your budget!!

It might seem counterintuitive or like a negotiating tactic where feel like you need to hold information back. But, in the same way that you wouldn't ask somebody to give you a quote on constructing a house without a budget, you wouldn't want to do that with the software either. And it's for your benefit.

If you know that your budget is $50,000 and you don't articulate that to the people that you're potentially going to work with, their estimation process is going to be purely based on every idea you've been able to put out there so far. If you tell somebody upfront that you have either a hard budget, restriction, or a range, you're much more likely to get everyone thinking about how to hit and stay within that number. It's really more about creating some boundaries around what this product might be, what the abilities are, and who it's serving within the price point that's out there.

Joining us today are Jonathan Sasse and Joseph Jackson, experts in business strategy and software development.

We answer questions like: What is digital transformation? How attainable is planning a digital transformation to act as an industry disruptor? What are the recommendations for companies just starting out on their journey? And what might be the first steps on the journey? Join us as we uncover the benefits, challenges, and strategies involved in embarking on a successful digital transformation.

Episode Highlights:

What is digital transformation?

• Definition of digital transformation and its significance in today's business landscape.
• Understanding the impact of technology on business processes, customer experience, and market competitiveness.

The attainability of planning a digital transformation

• Exploring the feasibility of implementing digital transformation as an industry disruptor.

Recommendations for companies starting out

• Practical advice and key considerations for organizations initiating their digital transformation journey.
• The importance of aligning digital transformation goals with overall business objectives and culture.
• The importance of listening to your customer

First steps on the digital transformation journey

• Outlining the initial stages of a digital transformation strategy.
• Identifying key stakeholders, aligning visions and goals, understanding customer needs

Overcoming uncertainty for business owners

• Addressing the concerns and uncertainties that arise during a digital transformation journey.
• Strategies for managing change, fostering organizational buy-in, and building a culture of innovation.

Role of AI and automation in digital transformation

• Exploring the intersection of digital transformation, artificial intelligence, and automation.
• How businesses can leverage AI and automation technologies to streamline operations, enhance customer experiences, and drive growth.

Common challenges on the digital transformation journey

• Identifying the hurdles organizations commonly face during their digital transformation efforts.
• Solutions and best practices for overcoming obstacles such as resistance to change, legacy systems, and talent acquisition.

Follow us on linkedin: https://www.linkedin.com/company/metova/

Main Points:

• Determine if the problem is unique to yourself or if it affects many people
• Research where people may be talking about this problem to learn more about the problem and people's needs
• Consider self-evaluation questions such as "What am I good at?" and "How can I add as much value to this as I can?"
• Figure out if you have specific expertise that can help you solve the problem where people may have failed in the past
• Determine if you have funding to tackle the project
• Decide between an out-of-the-box solution versus creating a completely custom application from scratch
• Know who your customers are and where they go for information
• Work with journalists your customers trust
• Market to the right people in the right place at the right time
• Consider starting with an MVP version of your product to gauge success before launch
• Ensure you only accept money from people who believe in your vision and product, and not just taking money from anyone

Conclusion:

Developing an app idea can be daunting, but by following the steps we discussed in this episode, you can increase your chances of success. Remember to do your research, evaluate yourself and your skills, and ensure that you have the necessary funding. Additionally, knowing your customers and marketing to the right people at the right time can make all the difference.

In this episode, we discuss the following topics with Andrew Cowart, CTO at Metova, and Joeseph Jackson, VP of Technology at Metova:

Importance of Communication:

Effective communication is critical to any successful project, and this is especially true when it comes to developing software. We recommend finding a tech partner who communicates clearly and regularly. A lack of communication can lead to delays, misunderstandings, and even project failure. Make sure your tech partner is willing to answer questions, provide regular updates, and give you access to their project management tools.

Local Options and Recommendations:

When looking for a tech partner, consider choosing someone who is local or has worked with trusted professionals or companies in your area. They may have worked with a great tech partner who they can recommend.

Using Clutch to See Reviews:

Clutch is a platform that allows you to read reviews and ratings of tech partners. It can be a great tool to use when searching for a tech partner. Look for a partner with a high rating, positive reviews, and a portfolio that includes projects similar to yours.

Choosing Between Fivver and an Agency:

Fiverr is a platform that allows you to hire freelancers for a variety of tasks, including software development. While this may seem like a good option, keep in mind that Fiverr freelancers may not have the same level of expertise and support as an agency. Agencies can offer more resources, experience, and project management tools. Consider your budget, timeline, and project needs before deciding between Fiverr and an agency.

Intellectual Property Ownership:

Make sure you discuss intellectual property ownership with your tech partner before beginning the project. You'll want to ensure that you own the code and any other intellectual property associated with the project. This can be especially important if you plan to sell your app or software in the future.

Having Access to the Source Code at All Times:

Make sure you have access to the source code at all times, even if you're not a developer. This will allow you to make changes, hire a new developer, or move to a new tech partner if necessary. Your tech partner should be willing to give you access to the source code and provide documentation to help you understand it.

Not Shopping Based on the Lowest Bidder:

Don't make the mistake of shopping based on the lowest bidder. Choosing the cheapest tech partner may lead to poor quality work, delays, and other issues. Instead, consider the value that a tech partner can bring to your project, including their expertise, communication skills, and project management tools.

Conclusion:

We hope these tips have been helpful for non-tech founders looking to hire the right tech partner for their business. With the right tech partner, you can turn your app or software idea into a successful reality.