
Sign up to save your podcasts
Or


In today's episode, we have an inspiring guest whose journey from student to tech leader is a testament to the power of ambition and education. We are excited to have Zach Little, VP of Technology at Metova, join us.
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!
Introduction:
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:
2. Insights into Strategy Reviews (00:02:34)
3.Tech Reviews Unveiled (00:04:19)
4.Preparing for the Sessions (00:05:19)
5. Complementary Roles of Strategy and Tech Assessments (00:07:02)
6.Post-Review Process and Reports (00:09:29)
Closing Thoughts:
Next Steps:
Schedule a Session today! https://metova.com/strategysession/
Outro:
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…
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?
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.
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 platforms do you want to be on? (by platforms, we mean the web, android applications, iOS applications, etc..).
How many people do you intend to use this application? Where are they?
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.
Don't get caught up on specific vendors or the cloud architecture setup you go with.
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.
Understand that it's pretty rare to build a software product and then just finish building.
Questions to ask tech agencies
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.
In this episode, we delve into the importance of digital transformation for companies.
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?
The attainability of planning a digital transformation
Recommendations for companies starting out
First steps on the digital transformation journey
Overcoming uncertainty for business owners
Role of AI and automation in digital transformation
Common challenges on the digital transformation journey
Follow us on linkedin: https://www.linkedin.com/company/metova/
In this episode, we discuss the next steps after coming up with an app idea, with guests Jonathan Sasse and Josh Duntz. We talk about the importance of determining if your problem is unique and whether a solution already exists. We also discuss the importance of self-evaluation and how to ensure that your app won't sink after development.
Main Points:
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 of Software Savvy, we discuss tips for non-tech founders looking to hire the right tech partner for their business. Building an app or software can be a daunting task, and choosing the right tech partner can make all the difference. In this episode, we'll talk about the importance of communication, local options and recommendations, how to assess between different providers (i.e., Fivver, freelancers, tech agencies), and the importance of intellectual property ownership, among other considerations when choosing your tech partner.
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.
From the publisher's feed