Podcasts about Balsamiq

Today we have another episode of Better Done Than Perfect. Listen in as we talk to Asia Orangio, founder and CEO of DemandMaven. You'll learn about the five growth levers you can pull, why you might be doing OKRs wrong, how to know which marketing programs to double down on, and more.Please head over to the episode page for the detailed recap and key takeaways.Show notesDemandMavenIn Demand Episode 26: What is the SaaS Black Hole?Managing SaaS Growth with Asia OrangioUserlist's email examples postsSignWell – example of a good SEO programAmplitude, Google Analytics 4, SegMetrics – marketing attribution toolsMetabase – business intelligence toolDovetail, Cognism, Balsamiq, Drift – good marketing program examplesMagicLibrary – ideas for adsProfitWell's hot sauce campaignFollow Asia on Bluesky and LinkedInThe Work by DemandMaven on SubstackThanks for listening! If you found the episode useful, please spread the word about this new show on Twitter mentioning @userlist, or leave us a review on iTunes.SponsorThis show is brought to you by Userlist — an email automation platform for SaaS companies. It matches the complexity of your customer data, including many-to-many relationships between users and companies. Book your demo call today at userlist.com.Interested in sponsoring an episode? Learn more here.Leave a ReviewReviews are hugely important because they help new people discover this podcast. If you enjoyed listening to this episode, please leave a review on iTunes. Here's how.

Why should your marketing evolve into programs? In this episode, we talk to Asia Orangio, founder and CEO of DemandMaven. You'll learn about the five growth levers you can pull, why you might be doing OKRs wrong, how to know which marketing programs to double down on, and more.Visit our website for the detailed episode recap with key learnings.DemandMavenIn Demand Episode 26: What is the SaaS Black Hole?Managing SaaS Growth with Asia OrangioUserlist's email examples postsSignWell – example of a good SEO programAmplitude, Google Analytics 4, SegMetrics – marketing attribution toolsMetabase – business intelligence toolDovetail, Cognism, Balsamiq, Drift – good marketing program examplesMagicLibrary – ideas for adsProfitWell's hot sauce campaignFollow Asia on Bluesky and LinkedInThe Work by DemandMaven on SubstackThanks for listening! If you found the episode useful, please spread the word about the show on Twitter mentioning @userlist, or leave us a review on iTunes.SponsorThis show is brought to you by Userlist — an email automation platform for SaaS companies. It matches the complexity of your customer data, including many-to-many relationships between users and companies. Book your demo call today at userlist.com.

English Edition: together with Meag Doherty and Zihao Lu I want to shine a light on UX/UI design in research and put the capital "D" back into it. The way we design our software and research projects shapes the way not only the way they are being used, but also how successful they will be. Links:https://www.figma.com/ Figma tool for wireframinghttps://balsamiq.com Balsamiq wireframehttps://www.bjfogg.com BJ Fogg home page with a mention of Persuasion Technology from 2002https://en.wikipedia.org/wiki/A/B_testing A and B testinghttps://kdl.kcl.ac.uk King's College Digital Laboratory (KDL)I'd like to thank the UNIVERSE-HPC project for the support of this podcast.Get in touchThank you for listening! Merci de votre écoute! Vielen Dank für´s Zuhören! Contact Details/ Coordonnées / Kontakt: Email mailto:peter@code4thought.org UK RSE Slack (ukrse.slack.com): @code4thought or @piddie US RSE Slack (usrse.slack.com): @Peter Schmidt Mastodon: https://fosstodon.org/@code4thought or @code4thought@fosstodon.org Bluesky: https://bsky.app/profile/code4thought.bsky.social LinkedIn: https://www.linkedin.com/in/pweschmidt/ (personal Profile)LinkedIn: https://www.linkedin.com/company/codeforthought/ (Code for Thought Profile) This podcast is licensed under the Creative Commons Licence: https://creativecommons.org/licenses/by-sa/4.0/

Minter Dialogue avec Jean-Joel Huber Jean-Joël Huber, précédemment PDG, Chairman et co-propriétaire de Movitex Sharing, gérant les marques de mode, Daxon et Balsamiq, s'est lancé dans une nouvelle aventure stimulante: Les Éditions du Brigadier. Cet éditeur cherche à faire découvrir aux lecteurs francophones des auteurs et pièces qui ont du succès dans leur territoire linguistique mais qui sont largement ignorés en France. Ils assument un rôle de défricheur et de passeur de cultures. Nous discutons de cette aventure, le sens, les choix d'oeuvres et les enjeux de la traduction, comment il navigue le marketing et la distribution, ainsi que les enjeux du leadership aujourd'hui.   Si vous avez des commentaires ou questions, merci des les envoyer pour courriel à nminterdial@gmail.com. Et si le podcast vous a plu, merci de prendre quelques instants pour laisser une revue/notation sur Apple Podcast. Sinon, vous pourrez me trouver @mdial ou en VF @mdialFR sur Twitter. 

Wireframing is an incredibly useful design technique to flesh out conceptual ideas and communicate them to others. However, with the advent of powerful prototyping tools, some designers may think of these as irrelevant or outdated practices. Leon Barnard, Content Manager at Balsamiq and co-author of the book Wireframing for Everyone, discusses why he thinks wireframing is not only still relevant, but essential for maximizing creativity and innovative thinking. Connect with Leon Barnard Balsamiq Wireframing AcademyWireframing for Everyone (book) by Michael Angeles, Leon Barnard, & Billy Carlson Related NN/g Articles & Training Courses How to Draw a Wireframe (Even if You Can't Draw) (free article) UX Basics: Study Guide (collection of free articles) UX Basic Training (UX certification course) UX Deliverables (UX certification course) Visual Design Fundamentals (UX certification course)

In this episode of Product Thinking, product experts Ellen Chisa, Partner at boldstart ventures, and Leon Barnard, Education Team Lead at Balsamiq, join Melissa Perri to discuss the importance of wireframing in product development. They explore the collaborative power of wireframes in product teams, using wireframes as conversation starters, and the benefits of designers having front-end coding knowledge for efficient product outcomes.

Are design leaders and their teams neglecting the power of wireframing in UX design? In the latest episode of UX Leadership by Design, Mark Baldino explores this question, and others, with Billy Carlson, a design leader and educator. The episode dives deep into the often underestimated process of wireframing, emphasizing its critical role in project development. Billy underscores the value of staying in the the "gray areas" of low-fidelity design early on, as it allows teams to refine their ideas, establish content structures, and secure stakeholder buy-in before transitioning to high-fidelity design. They also talk about Billy's recent book, "Wireframing for Everyone," which aims to democratize wireframing, making it accessible to both designers and non-designers. If you're a design leader in the UX field, this podcast episode offers a fresh perspective and actionable insights to elevate your team's design process.ABOUT OUR GUEST: Billy Carlson is a design educator at Balsamiq, where he helps new and non-designers learn best practices for all phases of user interface and digital product design. He teaches university-level UX and design thinking courses, and, as a designer since 2005, he's worked on myriad products and led large UX teams at various organizations.TOPICS:The Role of Wireframing in UX DesignImportance of Staying in Low FidelityStrategies to Encourage Collaboration in WireframingChallenges Faced by Design LeadersBenefits of Concept Development in DesignBalancing Control and Collaboration as a Design LeaderTransitioning from Individual Contributor to Design LeadThe Intersection of Design Leadership and EducationThe Process of Writing a UX Design BookEffective Communication in Early Design PhasesLINKS:Wireframing for Everyone: https://abookapart.com/products/wireframing-for-everyoneBalsamiq Wireframes Academy: https://www.balsamiq.com/learnBilly on LinkedIn: https://www.linkedin.com/in/billycarlsonBalsamiq: https://www.balsamiq.com/Fuzzy Math: fuzzymath.com Mark on LinkedIn: https://www.linkedin.com/in/markbaldino/

In this episode of SaaS Fuel™, Jeff Mains dives into the world of wireframing and design with Leon Barnard, the design education lead at Balsamiq and author of the book, "Wireframing for Everyone" and offers advice on maintaining a healthy work-life balance in remote work environment. With over 10 years of experience in UX design, Leon shared valuable insights into the world of wireframing and its role in the design and development process. He also highlights the key principles and techniques of wireframing, emphasizing the need for simplicity, ideation, and collaboration.Tune in to discover how wireframing can transform your design process and fuel your SaaS success.Key Takeaways[00:01:27] - Sharing a corporate vision.[00:05:33] - Simplify your vision, engage emotions, foster open dialogue[00:09:03] - Wireframing in design and development.[00:16:20] - Understand your audience before designing[00:19:12] - Design and user understanding.[00:24:05] - Wireframing for everyone.[00:28:13] - UX/UI design trends.[00:30:18] - Balsamiq's unique wireframing focus.[00:34:07] - Mistakes in SaaS wireframing.[00:38:21] - Maintaining work-life balance.[00:41:26] - The importance of building relationships.Tweetable Quotes"I felt like wireframe and low fidelity is a good way to have conversations with the right people." - 00:09:07 Leon Barnard"As much as it is nice to think of the idea of having one tool that does everything, I think that there's still a place for tools that just do one thing well." - 00:31:42 Leon Barnard"I think one is we just don't want to wireframe to feel so intimidating or even design or UI design overall to feel intimidating." - 00:24:05 Leon Barnard"I think wireframes are meant to be very approachable, something that anybody can do. - 00:11:30 Leon Barnard“Facts tell, but stories sell. And we all remember stories. And why is that? It's how we connect. It's how we share experiences. And our experiences, well, that is our story.” - 00:03:52 Jeff MainsSaaS Leadership LessonsSimplify to Amplify. When communicating your vision, it is crucial to keep it simple and easily understandable. Avoid complex explanations that may confuse or overwhelm your team. By simplifying your vision, you increase the chances of it being remembered and shared effectively.Engage the Emotions. Facts tell, but stories sell. Craft a narrative that hits the heart and makes your team see themselves as the heroes of the story. By making your team the hero, you create a sense of purpose and alignment that motivates them to execute the vision with enthusiasm.Foster Open Dialogue. Communication is a two-way street. Create a no-judgment zone for brainstorming and idea sharing. By fostering open dialogue, you empower your team to contribute their ideas and perspectives, leading to better alignment and collaboration.Start with Wireframing. Wireframing is like a digital sketch, a visual representation of your ideas. It's a powerful tool that anyone can use, not just designers or developers. It helps you flesh out your ideas and iterate before diving into UI design.Remote Work Culture. Remote work is here to stay, and companies need to adapt. Embrace collaborative tools and asynchronous workflows to replicate in-person experiences. Set boundaries and prioritize work-life balance to prevent burnout.Guest ResourcesLeon Barnard (Twitter): https://twitter.com/leonbarnardLeon Barnard (Linkedin):

Show some love for today's sponsor, MIRO. https://www.miro.com/podcast Hey Premium'ster! Thanks for supporting us and super happy to have you as a supporter of This is HCD! I'm delighted to have you with me for another cracking episode this time with Leon Barnard, co-author of the brand spanking new book on A Book Apart, called Wireframing for Everyone. Leon, Michael and Bill all work for one of my absolute favourite UX businesses, Balsamiq. A wire framing tool that when it came out in 2008, was revolutionary. It reduced the exclusivity around the capability of wire framing, and made it accessible overnight to teams and non-designers. It increased the quality of communication, it reduced meetings, it sped things up and enabled better outcomes for teams working in the product space. It wasn't perfect, it wasn't sexy, but it was powerful.  In this conversation, we chat about the self-imposed restrictions on the product, still owned by the original founder, Giacomo (Peldi) Guilizzoni who I can vividly remember answering my support tickets in the early days of the business, and it's awesome to see and hear what the culture is like within the business. But onto the book, all three of the co-founders worked on parts of this book, and we speak at length with Leon about the approach, the mindset of wire framing and how it unlocks blockers within teams. This book I believe would make for great gifts for teams to pass around the organisation to try and improve the wire framing capability as you've probably heard many many times on this podcast, prototyping is one of the most incredible skills to have for any change-makers, and this book helps provide the keys to people. Book: https://abookapart.com/products/wireframing-for-everyone Watch on YouTube: https://youtu.be/8mKcwLC1HYE

Is there “one best way” to use wireframes in your design process? Our guest today is Leon Barnard, education team lead at Balsamiq and co-author of Wireframing for Everyone. You'll learn about their journey of writing the book, how they think about wireframes as industry insiders, the different phases and types of wireframing, tips on asking and giving feedback, and more.Podcast feed: subscribe to https://feeds.simplecast.com/4MvgQ73R in your favorite podcast app, and follow us on iTunes, Stitcher, or Google Podcasts.Show NotesWireframing for Everyone — a book by Michael Angeles, Leon Barnard, and Billy CarlsonFollow Leon on Twitter and LinkedInBalsamiq Wireframing AcademyGet a copy of Wireframing for EveryoneThis episode is brought to you by Refiner. Capture actionable product and user feedback with in-product microsurveys. Measure NPS, continuously research users, assess product-market fit, and more. With Refiner, run any type of survey and precisely target the right users at the right time. To get our in-product survey best practices, download our free microsurvey database at refiner.io/database.Interested in sponsoring an episode? Learn more here.Leave a ReviewReviews are hugely important because they help new people discover this podcast. If you enjoyed listening to this episode, please leave a review on iTunes. Here's how.

Can you get the benefits of design sprints in less time? Our guest today is Teresa Cain, author of Solving Problems in 2 Hours. You'll learn about why she decided to condense the traditional sprints, what problems can be solved using this format, how to avoid bias in decision-making, and more.Podcast feed: subscribe to https://feeds.simplecast.com/4MvgQ73R in your favorite podcast app, and follow us on iTunes, Stitcher, or Google Podcasts.Show NotesSolving Problems in 2 Hours — Teresa's bookTreviPay — Teresa's place of workEpisode 131: Design Sprint with Jonathan CourtneyFigJam, Miro, Mural, InVision, Balsamiq — collaboration toolsUse their template on Figma2 Hour Design Sprints on UdemyCheck out Teresa's websiteConnect with Teresa on LinkedInThis episode is brought to you by Refiner. Capture actionable product and user feedback with in-product microsurveys. Measure NPS, continuously research users, assess product-market fit, and more. With Refiner, run any type of survey and precisely target the right users at the right time. To get our in-product survey best practices, download our free microsurvey database at refiner.io/database.Interested in sponsoring an episode? Learn more here.Leave a ReviewReviews are hugely important because they help new people discover this podcast. If you enjoyed listening to this episode, please leave a review on iTunes. Here's how.

Realizzare mockup: wireframes di template. E mi ricordo di Balsamiq: sul sito vedo quanto sono cresciuti.E insieme parliamo di come disponiamo i nostri computer nei nostri offici.Bella occasione.Vi aspetto su caffe20.it/patreon:contenuti in anteprimasenza pubblicitàoriginalisu richiesta

Ravi was previously CPO at Tinder, Product Director at Facebook, and VP of Product at Tripadvisor. Currently, he's co-founder and CEO of Outpace, a coaching platform designed to help people reach their professional goals. In today's podcast, we dive deep into Ravi's product strategy stack framework and how it was used to develop a powerful strategy at Tinder. We also cover his other popular frameworks—the frontier of understanding and exponential feedback—and how both of them can help you grow in your career. We discuss the differences between building product at a startup versus a large tech company, and how Ravi has had to shift his mindset as he's moved away from a product leadership role into a founder role. Finally, he shares a bit about how Outpace is using AI to amplify coaches and help make them more efficient and effective.—Find the transcript for this episode and all past episodes at: https://www.lennyspodcast.com/episodes/. Today's transcript will be live by 8 a.m. PT.—Thank you to our wonderful sponsors for supporting this podcast:• Merge—A single API to add hundreds of integrations into your app: http://merge.dev/lenny• OneSchema—Import CSV data 10x faster: https://oneschema.co/lenny• Miro—A collaborative visual platform where your best work comes to life: https://miro.com/lenny—Where to find Ravi Mehta:• Twitter: https://twitter.com/ravi_mehta• LinkedIn: https://www.linkedin.com/in/ravimehta/• Website: https://www.ravi-mehta.com/—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• Twitter: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—Referenced:Disclaimer: Lenny is an angel investor Ravi's company, Outpace• Reforge's Product Strategy Program created by Casey Winters and Fareed Mosavat: https://www.reforge.com/programs/product-strategy• Matt Mochary on Lenny's Podcast: https://www.lennyspodcast.com/videos/how-to-fire-people-with-grace-work-through-fear-and-nurture-innovation-matt-mochary/• Indie Hackers: https://www.indiehackers.com/• Everything Marketplaces: https://www.everythingmarketplaces.com/• The Product Strategy Stack: https://www.ravi-mehta.com/product-strategy-stack/• Balsamiq: https://balsamiq.com/• Set better goals with NCTs, not OKRs: https://www.reforge.com/blog/set-better-goals-with-ncts-not-okrs• Ravi's product manager's competencies framework: https://www.ravi-mehta.com/product-manager-roles/• Hooked: How to Build Habit-Forming Products: https://www.amazon.com/Hooked-How-Build-Habit-Forming-Products/dp/0241184835/• Working Backwards: Insights, Stories, and Secrets from Inside Amazon: https://www.amazon.com/Working-Backwards-Insights-Stories-Secrets/dp/1250267595• Ian McAllister on Lenny's Podcast: https://www.lennyspodcast.com/videos/what-it-takes-to-become-a-top-1-pm-ian-mcallister-uber-amazon-airbnb/• The Ezra Klein Show podcast: https://podcasts.apple.com/us/podcast/the-ezra-klein-show/id1548604447• Ezra Klein's AI episode: https://podcasts.apple.com/us/podcast/a-skeptical-take-on-the-a-i-revolution/id1548604447?i=1000592835492• Andor on Disney+: https://www.disneyplus.com/series/star-wars-andor/3xsQKWG00GL5• Airtable: https://www.airtable.com/• Superhuman: https://superhuman.com/• Descript: https://www.descript.com/•  Outpace: https://www.outpace.co•  Unlock Your Product Manager Potential: https://www.outpace.co/guides/unlock-your-product-manager-potential—In this episode, we cover:(00:00) Ravi's background(04:24) Why Ravi left Tinder, and what he's been up to recently (08:05) Differences between working at an established tech company vs. a startup (12:45) Why founders should network with “early-stage” folks(14:29) Why you need to do some research and relationship-building before starting your company(17:49) What the product strategy stack is and how to use it(22:08) Mission vs. vision(23:37) How Ravi developed his strategy framework at Tripadvisor (26:43) Why PMs should understand design, UX, and UI(28:20) Examples of the product strategy stack in action(32:42) Why Tinder resisted adding filters (34:10) Monetization features at Tinder and the “whales” who spend the most(38:18) How customer feedback led to new features at Tinder(42:28) Why goals come after roadmap in Ravi's framework(44:30) Tripadvisor's strategy for increasing bookings(47:25) How to set goals that drive outcomes(50:24) The four buckets of the frontier of understanding(51:38) Different methods for trying to hit goals(53:08) Understanding why you hit or missed your goal(54:34) The product management competencies framework(1:02:08) The exponential feedback framework(1:04:25) Why you should ask for feedback—and graciously accept it(1:06:05) How to determine the right amount of leadership your team needs(1:09:40) What selective micro-management is(1:12:25) How Outpace uses AI to assist in coaching(1:15:24) Lightning round—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com. Get full access to Lenny's Newsletter at www.lennysnewsletter.com/subscribe

Although many of us product people have UX and UI designers on our teams, it is not a bad idea to know how to use some of the tools used for designing our products, especially in the wireframing phase, when the design are low-fidelity, and we need to figure out what the best way to contain data on the screens, and the most efficient way for users to use the system. In the series, we covered Figma, Miro, Lucidchart and Balsamiq. In this episode Matt and Moshe met again to summarize what they learned.Some of the discussion points include:Low fidelity vs. high fidelity, and how the tool we choose can influence the steps we take in the designThe importance of not skipping the low fidelity, wireframing step, and why jumping right away to high fidelity can be a problem to the usersOne tool that does it all vs. specialized tools for each stepCollaboration with the help of the toolAnd more! * Product for Product sitehttps://www.spreaker.com/show/product-for-product * You can find the podcast's page, and connect with Matt and Moshe on Linkedin: - Product for Product Podcast - linkedin.com/company/product-for-product-podcast - Matt Green - linkedin.com/in/mattgreenanalytics/ - Moshe Mikanovsky - linkedin.com/in/mikanovsky/ *Note: any views mentioned in the podcast are the sole views of our hosts and guests, and do not represent the products mentioned in any way.Please leave us a review and feedback ⭐️⭐️⭐️⭐️⭐️

Welcome to the UX/UI and Wireframing series, where we explore different tools that Product Managers use in the design process, either on their own or with the help of a UX/UI Designer. In this episode, Matt and Moshe had the pleasure of speaking with Sufian Siddiqi, Lead Product Manager at Lucid Motors, about the tool Balsamiq. Sufian has been using it for years now, since it was in beta. He loves the simplicity of the product, especially at the early stages of a product ideation.In the episode, Sufian talks about:Why he uses Balsamiq How using a more designer oriented system runs the risk of skipping the wireframing step Collaboration and prototyping with BalsamiqUsing templateLearning how to wireframe with Balsamiq's resources And so much more!To learn more about Balsamiq:https://balsamiq.com/Connect with Sufian:https://www.linkedin.com/in/sufian/Connect with Matt and Moshe on LinkedIn:*Matt - www.linkedin.com/in/mattgreenanalytics*Moshe - www.linkedin.com/in/mikanovsky *Note: any views mentioned in the podcast are the sole views of our hosts and guests, and do not represent the products mentioned in any way.Please leave us a review and feedback ⭐️⭐️⭐️⭐️⭐️

Terminals seem like the very lowest common denominator for software platforms. They have to work over SSH. They only show text. You can't do much with them. Or can you? Will McGugan and team have been building Textual (based on Rich) which looks more like an animated web app than a terminal app. And he has learned a bunch of lessons trying to maximize terminal based apps. He's here to share his 7 lessons he's learned while building a modern TUI (text user interface) framework. Links from the show Will McGugan: @willmcgugan 7 things I've learned building a modern TUI framework post: textualize.io Prior Talk Python Episode: talkpython.fm Textualize: textualize.io Kitty terminal: sw.kovidgoyal.net Pydantic Immutability: pydantic-docs.helpmanual.io Monodraw: monodraw.helftone.com Async's lru cache: github.com Rich CLI: github.com Nerd Fonts: nerdfonts.com Oh My Posh: ohmyposh.dev Python Object Allocator ASCII Art: github.com Balsamiq wireframes: balsamiq.com Watch this episode on YouTube: youtube.com Episode transcripts: talkpython.fm --- Stay in touch with us --- Subscribe to us on YouTube: youtube.com Follow Talk Python on Twitter: @talkpython Follow Michael on Twitter: @mkennedy Sponsors Microsoft Sentry's DEX Conference AssemblyAI Talk Python Training

Welcome to the UX/UI and Wireframing kickoff episode. Matt and Moshe met to discuss what UX/UI design and Wireframing systems are all about.Although they debated whether to have a dedicated series for each of them, one for UX/UI design systems such as Figma or Invision, and one for Wireframing systems like Balsamiq, they decided on merging these into one series. Reason is that Product Managers don't usually do a lot of the UX/UI design, and are more involved in the wireframing process. Some systems are dedicated to wireframing, while others are more geared to the UX/UI design, and still allow the Product Managers to participate. While other systems, such as Miro, is more of a broad whiteboard collaboration platform, which lends itself to wireframing.In this episode, Matt and Moshe discuss some of they expectations from the series and what they would like to learn, such as:* User friendliness of the various platforms* The collaboration aspects* Prototyping* And more! The products we will discuss include:* Figma* Lucidchart* Miro* Balsamiq* and moreConnect with Matt and Moshe on LinkedIn:*Matt - www.linkedin.com/in/mattgreenanalytics*Moshe - www.linkedin.com/in/mikanovsky *Note: any views mentioned in the podcast are the sole views of our hosts and guests, and do not represent the products mentioned in any way.Please leave us a review and feedback ⭐️⭐️⭐️⭐️⭐️

We are joined by a good friend of the podcast, Peldi Guilizzoni,  to discuss how to go about sponsoring events, newsletters, and podcasts to promote your product. In particular we talk about creative approaches that make your sponsorship stand out.Mentioned in this episode:Peldi's company, Balsamiq, a low-fidelity wireframing tool.Steve's company, Feature UpvoteEd's company, OpenCageSteve on TwitterEmail: steve@bootstrapped.fm   

Today we have another episode of Better Done Than Perfect. Listen in as we talk with Chris Silvestri, copywriter, designer, and founder of Conversion Alchemy. You'll learn the strategies to increase conversions on landing pages and blog posts, the power of heatmaps and usability testing, resources for further CRO learning, and more.Please head over to the episode page for the detailed recap and key takeaways.Show notesConversion Alchemy — Chris's copywriting and design businessQuinn Zeda — founder of Conversion CrimesClickUp — an example of a cohesive experienceHotjar, Smartlook — tools for measuring user behaviorClickUp, Balsamiq — examples of great blog designBaymard Institute — group that has research on usability studiesCopyhackers — a popular resource for conversion copywritersMECLABS Institute — resource for understanding buying behaviorConversion Alchemy Journal — Chris's daily newsletter Follow Chris on TwitterSponsorThis show is brought to you by Userlist — the best tool for sending onboarding emails and segmenting your SaaS users. To follow the best practices, download our free printable email planning worksheets at userlist.com/worksheets.Interested in sponsoring an episode? Learn more here.Leave a ReviewReviews are hugely important because they help new people discover this podcast. If you enjoyed listening to this episode, please leave a review on iTunes. Here's how.

How can copy work alongside design to increase SaaS website conversions? In this episode, we talk to Chris Silvestri, copywriter, designer, and founder of Conversion Alchemy. You'll learn the strategies to increase conversions on landing pages and blog posts, the power of heatmaps and usability testing, resources for further CRO learning, and more.Visit our website for the detailed episode recap with key learnings.Conversion Alchemy — Chris's copywriting and design businessQuinn Zeda — founder of Conversion CrimesClickUp — an example of a cohesive experienceHotjar, Smartlook — tools for measuring user behaviorClickUp, Balsamiq — examples of great blog designBaymard Institute — group that has research on usability studiesCopyhackers — a popular resource for conversion copywritersMECLABS Institute — resource for understanding buying behaviorConversion Alchemy Journal — Chris's daily newsletterFollow Chris on TwitterThanks for listening! If you found the episode useful, please spread the word about the show on Twitter mentioning @userlist, or leave us a review on iTunes.SponsorThis show is brought to you by Userlist — the best tool for sending onboarding emails and segmenting your SaaS users. To follow the best practices, download our free printable email planning worksheets at userlist.com/worksheets.

Twenty pages into reading his first business book, Peldi Guilizzonni (@peldi) closed it for good and told himself, "This is not for me. I'm never going to start a business. It's insane." Not long after that, he rolled up his sleeves and got started building Balsamiq Mockups, which would go on to employee dozens of people, serve thousands of customers, and generate over $6M per year in revenue. Over ten years later, it's still going strong. Learn about the path Peldi took to get where he is today, why he's a legend among bootstrappers, and how he's building a business that's meant to last.Transcript, speaker information, and more: https://www.indiehackers.com/podcast/085-peldi-guilizzoni-of-balsamiq

Frequent guest Peldi, founder of Balsamiq, makes another welcome appearance.We talk about some ways to strengthen company culture in a fully-remote team, we discuss advice that Peldi often gives to first-time entrepreneurs, and Peldi tells me why he might finally start with traditional product marketing - 14 years after he launched his product.Find out more about Balsamiq's Office Hours.  

In this episode you will discover important strategies that drive a business forward. Procedures such as the importance of customer feedback to create a product or service that they really need, using automation to speed up repetitive chores, and developing a remote work culture that embraces the team spirit.Listen in as Peldi explains his thought processes on boosting productivity within his fully remote workplace and reveals the one important skill that everyone needs. He walks us through how he and the team at Balsamiq do more with less.

We're back with Val Liberty from Balsamic, talking about having interactions with hard customers. You know...those people you can never please. One way to combat the burnout of dealing with terrible customers over and over, Balsamiq has created a culture of trust and boundaries in their employees to empower them even in the worst of circumstances. It's worth a listen just to hear how they de-escalate and diffuse and send people off with a smile.

Sviluppare sul web. Non solo mockup con Balsamiq. Ma un vero gestionale con tutti gli eventi già definiti, vanno solo indicate le azioni.Il video in home e' pazzesco. retool.com il nome del linguaggio.Sfoglia le fonti citate nel podcast su: www.caffe20.it/link e cerca coding=*_*=Caffe20.it il podcast: - Linkografia: www.caffe20.it/link- Sito: www.caffe20.it/play- News: t.me/caffe20- Gruppo: t.me/caffe20group- Alexa: apri caffè due punto zero- Contatti: info@caffe20.it- Telefono: 02 4548 9591Supporta con domande e con donazioni !- www.caffe20.it/sostenitori=*_*= ADV:COOKIEIl KIT è arrivato su: www.cookiekit.it/ondemandLe LIVE continuano su: www.cookiekit.it/liveGratis ogni giorno: privacykit.it/podcast e privacykit.i/rssPRIVACYGDPR: Le basi operative, su Udemy: www.caffe20.it/corsi/privacyPASSWORDGestirle facilmente: www.caffe20.it/corsi/passwordINFLUENCERDiritto d'autore e strategie legali: www.caffe20.it/corsi/influencerPODCASTINGDiventa podcaster registrando: www.caffe20.it/corsiECOMMERCERaccogli gli ordini, evadili in automatico, prepara la bozza di fattura elettronica: www.fatturami.itRECENSIONI FALSEDifenditi dalle Fake Reviews: www.civile.it/internet/visual.php?num=95680BLOCKCHAINLibro su Bitcoin e Blockchain: prenotalo senza impegno scrivendo info@legalkit.it o t.me/iusondemand indicando il prezzo che lo pagheresti. Vale fino al 30.11.2021ACCESSIBILITA' e USABILITA' DIGITALIControlla l'usabilità e gli aspetti legali di sito, app e assistenti: www.Controllosito.itCHI E' SPATARO VALENTINO ?Sviluppatore dal 1984 e giurista dal 1995. Privacy e sviluppo servizi online.=*_*=... e condividi caffe20.it con gli amici !

Alberto Forni is a Software Engineer at Balsamiq where he works on the Balsamiq Wireframes development. He is passionate about programming, Design, User Interface, and, more broadly, he loves everything that has a plug :D Jessica Orellanes is a qualitative user experience researcher at Balsamiq. After 10+ years in Communication and Digital Marketing, she found real love in UX Research. Now it is her passion and her job. During this episode we cover: 00:00 - https://www.prodcamp.com (ProdCamp) User Feedback & Product Management Platform 00:54 - Intro 02:57 - Customer Research at Balsamiq 05:20 - How The Research Interview Works 07:57 - Peers & Improve Organization Communication Strategy 10:12 - Time zones & The "Golden Hour" 12:19 - Product Road map & Decisions 16:55 - Tips About Starting a Customer Research on a SaaS 21:23 - Adding Value To Interaction With Customers 25:21 - How Balsamiq is Monitoring & Improving With/Without Metrics 29:10 - Why Alberto Doesn't Have a Balsamiq Pet 29:25 What Pet Alberto Would Adopt + Name 29:54 - Alberto's Suggested Dishes to Try in Bologna 30:31 - Why Jessica Doesn't Have a Balsamiq Pet 31:52 - What Pet Jessica Would Adopt + Name 32:35 - What Superpower Jessica Would Want 34:15 - Career Path Tips From Alberto & Jessica 35:51 - What Motivates Them to Keep Working Hard Get in Touch With Alberto & Jessica: https://twitter.com/albertoforni (Alberto's Twitter) https://twitter.com/balsamiq (Jessica's Twitter) Tag Us & Follow: https://www.facebook.com/SaaSDistrictPodcast/ (Facebook) https://www.linkedin.com/company/horizen-capital (LinkedIn) https://www.instagram.com/saasdistrict/ (Instagram) More About Akeel: https://twitter.com/AkeelJabber (Twitter) https://linkedin.com/in/akeel-jabbar (LinkedIn) https://horizencapital.com/saas-podcast (More Podcast Sessions)

Billy Carlson is a Design Educator at Balsamiq where he helps new and non-designers learn best practices of interface and digital product design. He's been a designer for over 15 years and has worked on many types of projects. Previously, he led large UX teams at various corporations' internal design groups. During this episode we cover: 00:00 - Impekable Bay Area Product Development Agency 00:45 - Intro 02:08 - Basics of Wireframing & How to Get Started 04:22 - Taking Notes on Wireframing References 05:30 - First Steps on Prototyping 08:06 - Content First Design 09:41 - How SaaS Founders Can Apply Content First Design 10:48 - The Educational Part of The Design Process 12:57 - Principles of Effective Wireframing 21:30 - Expectations & Productivity on Leading Design Team 24:05 - Billy's Routine To Get Into a Creative State 26:02 - Best Dog Breed as Companion for Wireframing 26:50 - What Pet Billy Would Adopt 27:48 - Billy's Favorite Hobbies To Get Into a Flow State 29:11 - Billy's Favorite Thing About Working at Balsamiq 30:08 - Path Tips for Design Career Links: https://balsamiq.com/learn/articles/ten-principles-effective-wireframes/ (Ten Principles of Effective Wireframes) Get in Touch With Billy: https://twitter.com/billycarlson (Billy's Twitter) Tag Us & Follow: https://www.facebook.com/SaaSDistrictPodcast/ (Facebook) https://www.linkedin.com/company/horizen-capital (LinkedIn) https://www.instagram.com/saasdistrict/ (Instagram) More About Akeel: https://twitter.com/AkeelJabber (Twitter) https://linkedin.com/in/akeel-jabbar (LinkedIn) https://horizencapital.com/saas-podcast (More Podcast Sessions)

- Passive Income and EntrepreneurshipThis episode of the Bootstrapped Founder podcast is sponsored by Balsamiq, makers of Balsamiq Wireframes, the OG of low-fidelity wireframing tools.The guest sponsor this week is Cold Email for Interesting People.If you want a promo code for Balsamiq, go to balsamiq.com/go/bootstrapped-founder/

- Building in Public: What to Share at Which Stage of Your JourneyThis episode of the Bootstrapped Founder podcast is sponsored by Balsamiq, makers of Balsamiq Wireframes, the OG of low-fidelity wireframing tools.The guest sponsor this week is Innowayt.If you want a promo code for Balsamiq, go to balsamiq.com/go/bootstrapped-founder/

- Building in Public: Taking BreaksThis episode of the Bootstrapped Founder podcast is sponsored by Balsamiq, makers of Balsamiq Wireframes, the OG of low-fidelity wireframing tools.The guest sponsor this week is Logology.If you want a promo code for Balsamiq, go to balsamiq.com/go/bootstrapped-founder/

- Building in Public: Balancing Building and SharingThis episode of the Bootstrapped Founder podcast is sponsored by Balsamiq, makers of Balsamiq Wireframes, the OG of low-fidelity wireframing tools.The guest sponsor this week is Typesense.If you want a promo code for Balsamiq, go to balsamiq.com/go/bootstrapped-founder/

- Too Little, Too Much: Advice and How to Take ItThis episode of the Bootstrapped Founder podcast is sponsored by Balsamiq, makers of Balsamiq Wireframes, the OG of low-fidelity wireframing tools.The guest sponsor this week is Indie Worldwide.If you want a promo code for Balsamiq, go to balsamiq.com/go/bootstrapped-founder/

- BurnoutThis episode of the Bootstrapped Founder podcast is sponsored by Balsamiq, makers of Balsamiq Wireframes, the OG of low-fidelity wireframing tools.The guest sponsor this week is Podopi.If you want a promo code for Balsamiq, go to balsamiq.com/go/bootstrapped-founder/

- What Founders Can Learn From the Facebook OutageThis episode of the Bootstrapped Founder podcast is sponsored by Balsamiq, makers of Balsamiq Wireframes, the OG of low-fidelity wireframing tools.The guest sponsor this week is Dawn.If you want a promo code for Balsamiq, go to balsamiq.com/go/bootstrapped-founder/

- Copycats and EnduranceThis episode of the Bootstrapped Founder podcast is sponsored by Balsamiq, makers of Balsamiq Wireframes, the OG of low-fidelity wireframing tools. If you want a promo code for Balsamiq, go to balsamiq.com/go/bootstrapped-founder/

Build a SaaS app!" they said... "It'll be great!" they said...it turns out, running an online service Is a big pain in the SaaS. In this talk I will tell you all about designing, building, selling, scaling, maintaining and supporting balsamiq.cloud, the online version of Balsamiq Wireframes. I'll focus on 'the things they don't tell you' and even give you the dirt about a massive data-loss incident from May 2018. Fasten your seatbelts, there will be turbulence! --- Giacomo 'Peldi' Guilizzoni is a programmer turned entrepreneur, who founded Balsamiq in 2008 and has been learning how to run and grow the company ever since. He has spoken at Microconf a few times along the way, to share his learnings and, mostly, his mistakes. He still loves to code, when he's allowed to by his team. :) Check out Peldi’s MicroConf speakers page for more talks → https://microconf.com/speakers/peldi-... https://microconf.com #microconf #microconfeurope2019 MicroConf Europe 2019 MicroConf Connect → http://microconfconnect.com Twitter → https://twitter.com/MicroConf E-mail → support@microconf.com MicroConf 2021 Headline Partners ► Stripe https://stripe.com Twitter → https://twitter.com/Stripe

If you don't already know, there's a difference between web design and web development. Both function differently, and both should typically be done separately and treated as individual parts of your website design process. While I don't believe in unicorns or the infamous “jack of all trades,” I do believe that you can find a good designer AND a good developer, who may or may not be on the same team, who will work well together on your project. Combine those two parts with great content and you're all set for the website you need to help your business succeed. The cohesiveness between all three parts is vital to the overall functionality and style of your website — one really can't exist without the other. Design vs. Development The first part of creating a website is the design. This is what your site will look like, how it will function, what images you'll want, etc. You can find many design templates, where you simply change the colors and content and your developer sets it to go live when ready. If you already have a website up, your first step will be to figure out what works, what doesn't, what changes you need and which parts of your current website you want to keep. You'll want to look at your competitor's websites and take note of what you love, hate, or feel indifferent toward. This is the discovery part of your process. You can choose to perform this due diligence yourself, but if it's within your budget, you may prefer to have the designer and developer (who may both be working in one agency) do the discovery for your business. Don't forget to find out what they will be charging you for discovery and revisions. If you're doing this part yourself, then you'll want to start by creating a map of your website to pass along to the designer, who will be able to build a wireframe.  Every agency, design shop and designer approaches the wireframing from a different angle. They may use mockup tools like Balsamiq, Invisionapp, Mockingbird, UXPin, Visio and others to get you a prototype. You should expect to pay for this service. Think of it like building a house. You pay the architect to create the basic design. If you choose to hire them to create the blueprint, then you'll have to pay for the plans too. If the architect happens to work with a builder, who in this case would be the developer, you may or may not choose that builder to build the house. A web designer may work closely with a particular developer, and you can use your own discretion to choose if you'll also work with that developer. Don't forget to consider if your business will need a back-end for customers to log in, make payments, etc. This is not included in a regular website design, and will involve additional costs, planning and more. It's also important to keep in mind that web design takes time. I would say that the biggest complaint I hear from businesses is that the web designer or agency hired to design/develop their website took twice as long as what they agreed to complete the website. This can be very frustrating and can change your experience completely, leaving you unsatisfied due to the timeline. Before moving forward with your new website, here are 12 questions you should ask the designer or agency you hire to be clear on timelines and more: 12 Questions to Ask Your Designer: Can you send me a list of sites you designed? Do you charge hourly or by project? Do you have a project manager or 1 contact for the entire project? How many revisions am I allowed? What are the payment terms? What CMS will you build my website in? What support do you offer once the site is live? Do you work using templates/themes or build custom sites? Will the website be responsive? Who will write the content? What services do you provide? What kind of results can I expect? The Next Steps Once you're clear on what you can expect from your designer, you can start thinking about your website development. The designer will create static images and wireframing, while the developer will put those designs in motion, creating the code, working forms and more for your site. Your website development will bring your design to life, and a good developer is key, as there is always some back and forth to fix and revise your site. You'll want to work with someone who is responsive and understands clearly what you're trying to achieve with your website. If you're looking to sell products on your site, this will add a whole new level to the need for a great web developer. Lastly, your website design and development will absolutely not work smoothly without the right content. Your content is a key component because it is telling your customers and potential customers who your business is and why they should hire you or choose your company for their product or service needs. Your website's content is doing the job of delivering the message for your business. When writing your content, you should answer the following: What do you want to achieve?  What should customers think of your business?  What do you want your business to be known for?  And how will you communicate those messages to your customers?  Well-written content will do the job of helping customers understand who you are, why you do what you do, and why you are the best choice for them.  Website design and development, along with great content, can help your business achieve the sales goals you've set. Asking all the right questions will help you choose the right web designer and developer to create your unique space on the web. Check out the blog post for more info.  

12 Questions You Need To Ask a Website Designer or Developer   If you don't already know, there's a difference between web design and web development. I don't believe in unicorns or jack of all trades, but I do believe that you can find a good designer and a good developer who mayor may not be on the same team and work well together on your project. It's important to understand what the designer and developer which may be working in 1 agency will be charging you for discovery and revisions. If your budget is set then you'll want to start by creating a map of your website and the designer will be able to build a wireframe. Every agency, design shop and design approaches this from a different angle. They may use mockup tools like Balsamiq, Invisionapp , Mockingbird, UXPin , Visio and others to get you a prototype. You should expect to pay for this service. Think of it like building a house. You pay the architect to create the basic design. If you choose to hire them to create the blueprint then you'll have to pay for the plans too. If the architect happens to work with the builder, you may or may not choose that builder to build the house. I would say that the biggest complaint I hear from businesses is that the web designer or agency hired to design/develop their website took twice as long as what they agreed to complete the website. Make sure that the designer or agency you hire can give you clear timelines by asking these questions: Can you send me a list of sites you designed? Do you charge hourly or by project? Do you have a project manager or 1 contact for the entire project? How many revisions am I allowed? What are the payment terms? What CMS will you build it in? What support do you offer once the site is live? Do you work using templates/themes or build custom sites? Will the website be responsive? Who will write the content? What services do you provide? What kind of results can I expect?

You can find articles on the topics discussed in the episode here:- ✍️  Customer Retention: How to Keep Them AroundAs mentioned in the episode, feel free to check out my book Zero to Sold. Here's the launch tweet.Undock sponsors this episode of the Bootstrapped Founder Podcast. Balsamiq provides this sponsored airtime. Please check out both — they're awesome.

You can find articles on the topics discussed in the episode here:- ✍️  Customer Exploration: Seeing Through Your Customer's EyesHipSpec sponsors this episode of the Bootstrapped Founder Podcast. Balsamiq provides this sponsored airtime. Please check out both — they're awesome.

You can find articles on the topics discussed in the episode here:- ✍️  Being Small Is a Benefit: How to Leverage Being a BootstrapperOutseta sponsors this episode of the Bootstrapped Founder Podcast. Balsamiq provides this sponsored airtime. Please check out both — they're awesome.

You can find articles on the topics discussed in the episode here:- ✍️  Spreading the Word: How to Do Marketing on a Shoestring BudgetFeature Upvote sponsors this episode of the Bootstrapped Founder Podcast. Balsamiq provides this sponsored airtime. Please check out both — they're awesome.

You can find articles on the topics discussed in the episode here:- ✍️ Seller Beware: Pricing Models That Can Break Your BusinessLinks mentioned in part two:https://untools.co/https://www.teachthought.com/critical-thinking/the-cognitive-bias-codex-a-visual-of-180-cognitive-biases/If you want to be inspired by Seth Godin, please read https://seths.blog/2020/05/dancing-with-tech/Libpixel sponsors this episode of the Bootstrapped Founder Podcast. Balsamiq provides this sponsored airtime. Please check out both — they're awesome.

You can find articles on the topics discussed in the episode here:- ✍️  Not All Subscriptions Are Equal: Offer Yearly Plans from the StartThis episode of the Bootstrapped Founder Podcast is sponsored by Treendly. This sponsored airtime is provided by Balsamiq. Please check out both — they're awesome.

You can find articles on the topics discussed in the episode here:- ✍️ Not All Subscribers Are Equal: How to Deal with Plans That No Longer Work- ✍️ Profit-Sharing as Employee Compensation for BootstrappersThis episode of the Bootstrapp ed Founder Podcast is sponsored by DrawSQL. This sponsored airtime is provided by Balsamiq. Please check out both — they're awesome.

You can find the promo code provided the sponsor of this show, Balsamiq, right here.

Peldi, the CEO of Balsamiq, embodies some of the best attributes of both successful CEOs and product managers. He is always learning and looking to learn. He strives to deliver not only a product that his customers love, but to build a company, culture and community that help his customers beyond the ordinary product features. Despite his jokes to the contrary, Peldi is in no way clueless, his humility and thoughtful approach to his business are refreshing and he should serve as an inspiration to entre

Show Notes: 01:02 - Why outside-in development? 05:50 - Best Practices and Implementation 09:35 - API Iteration and Design 18:31 - Is outside-in development a timeless approach to software development? 24:10 - Outside-in Creation 28:37 - Summarizing Outside-in Development and What it means to the Frontside Resources: Sketch InVision Balsamiq pretender Ember CLI Mirage bigtest Transcript: CHARLES: Hello everybody and welcome to The Frontside Podcast episode 96. My name is Charles, I'm a developer here at the Frontside. And your podcast host in-training with me today is Jeffrey. JEFFREY: Hello. CHARLES: Hello, Jeffrey. And Arash. ARASH: Good morning. CHARLES: Yeah, how are you doing? ARASH: Doing great. Thank you. CHARLES: All right. So, today this is going to be a little bit of an internal powwow where we're just going to talk about some of the patterns that we see as we develop software and just kind of a little bit of a chat on the way we do it. So, we're going to be talking today, I guess we could do like a little bit of a spoiler and just kind of co lead with what we're talking about. ARASH: Which is... CHARLES: Which is... ARASH: Drum roll... CHARLES: Outside-In development. And it's kind of the way that we've just naturally gravitated towards, towards developing software here. ARASH: So first question is why we gravitated toward that. CHARLES: I could just tell you kind of our personal history on this. Is that, I guess it was, would you say like around 2007, something like that kind of the pattern of like REST services got like really well established. ARASH: Sure, that's accurate enough. CHARLES: Yeah. It's like around mid-2000's. And so people just went kind of, you know, cuckoo for Cocoa Puffs except APIs instead of Cocoa Puffs. So it was like all the talk was about your API, what's going to be your API, and how are you going to present this to the world? And oh my goodness, you're opening up your system for extension by developers and it's really fantastic. So, it kind of became the norm, I feel, from that point forward to be thinking about what is the API that I'm going to be presenting rather than what's the application. ARASH: That's your starting point. CHARLES: Yeah, that's your starting point. So a lot of development and getting like a lot of frameworks came along to make API development really simple, regardless of run time. It was really just really simple to just set up API. And so, a lot of people did that and I think there was value in that and that you're thinking kind of about your external domain model, like how you're going to present yourself to the world. And so you really are focused on the constraints and the abstractions that you want to present and how you want to hide all the messy complexity behind your system. But the problem that you get into is in those days, especially on the web, the clients were very closely aligned with the APIs. If you're coming like from a Rails backend, you almost had one for one between your pages and your API. If I've got a user's end point, I'm going to have a user's management page. And I think as clients became more stateful and more of the kind of interactions were ported over to the client, that synchronization and one to one mapping between what your API look like and what your interface look like, that started to crumble and disintegrate. And now I think that it's actually quite, I mean there are still clearly analogs because you're talking about the same entities. But your client is really now a full-featured application. And it's got complex rendering logic, it's got complex state management, it's got all these things that happened completely and totally separate from your API endpoints. JEFFREY: And your UI ends up being aware of relationships between models. So yeah, it's just so much more sophisticated than what we used to need to do when everything was server-side rendered. When you're dealing with a heavy client side app, your API needs to be quite a bit more flexible really. CHARLES: Right. And so what we were finding was that we'd often have to change the API significantly in order to support complex interaction on the client. But the problem is, is if you've started with your API, you've invested a lot of development, you've invested a lot of design and you've really laid down not just that design, but also the infrastructure and the operations to make it real, it can be very hard to change. And so, it can exclude a lot of the desirable interactions that you would like to have merely by virtue of the fact that it's set in stone. So I think that's kind of why we found ourselves... JEFFREY: Why we discovered that inside out wasn't quite working for what we're doing anymore. CHARLES: Yeah, exactly. It was like having a rock solid API was actually a drawback rather than an asset, whereas 10 years earlier it was an asset. And so it really, kind of having that insight made us step back and wind it back and say, "OK, where is the natural starting point? Where do we want to start?" ARASH: So philosophically, what does Outside-In development mean to the Frontside? JEFFREY: It means that instead of starting with the API, looking at actually the workflow is instead we start with what's the UI. What is the client side app going to look like and what are the needs of that client side app? And that drives the development of the API rather than solely, I guess you could say, the business models that would have previously been the initial driver for what that would look like. CHARLES: Right, exactly. Letting the business models be kind of a function of the desired interaction or the desired experience and then letting it proceed from there. So really is yeah, it's starting from kind of what does the person using your system going to touch rather than what is the computer using your system going to touch. ARASH: And so if one of our listeners is interested in Outside-in development, what kind of tenets would you recommend they follow and what are some of the best practices you can put into place to align well with this kind of thinking that we're talking about here? CHARLES: I think that's a good question because there's obviously the philosophy of it, but then there's the practice and the implementation and what does that mean. And there's a lot. There's a lot of just kind of the way you approach the problem and then the tools that you're going to use. I don't know, Jeffrey, which ones should we tackle first? JEFFREY: Let's tackle the tools. Why not? We'll go backwards. We probably should cover other things first, but why not? CHARLES: We'll tackle the tools? All right, and this is actually a question I want to throw your way too is at what point do you...because you want to start really with having a good design, like a good wireframe? Do you prefer to start with say like something in InVision or Sketch or do you like to proceed straight to a working implementation? JEFFREY: For me, it usually depends on how complicated of an app it's going to be. If it is something that's, I'm just dealing with like some crud operations, a lot of times I'll just go straight to the HTML and like starting to build that in actual JavaScript and we'll probably talk about the fake backend for that. But yeah, it versus something that's a little more complicated that has maybe a more novel approach or particularly interesting workflow or something that's going to be pretty difficult to code. That's when I'll start on in Sketcher, InVision, or a tool like that. CHARLES: I think in the last project, we used Balsamiq. I mean, we don't want to get caught up on like tools, but I think that's a great tool because the other thing we did is it wasn't just one designer doing it. We actually had all of our developers going and writing Balsamiq sketches for the features that they were going to be implementing because it really means that they're going to actually put themselves in the shoes of someone using it and they're going to be thinking about what it's like to be a user. Because they've got to start drawing the boxes and lines and the buttons that people are going to click in and the text fields in which they're going to communicate with the system. JEFFREY: And what was awesome about using a sketchy type of style like Balsamiq is that it removes the developers from thinking too much about having to make sure this headline is exactly the right font size, that I'm using all the exact right colors. Like, don't worry about that yet. Let's just get the wireframes in this sketchy style first and then we can work from there. CHARLES: Because it really is. It's very valuable to have this process for yourself as one single developer to be able to view it from the outside in. And I think that looking at it one way, that's truly what it means to be full stack is that you can put yourself in the shoes of every piece of the system at each point. So I can put myself in the user's shoes, I can put myself in the client's shoes. When I say 'client', like the actual browser, the browser's shoes. I can put myself in the server shoes and I can have that perspective of each part. JEFFREY: So that got me thinking about what browsers would wear what kind of shoes, but we'll leave that conversation for another time. Who'd wear the Chrome shoes? ARASH: Chrome is definitely Nike, for sure. Speed. JEFFREY: So back to the tool. CHARLES: Just like Safari, like Hugo Boss. ARASH: It's like, yeah, that's pretty close. Netscape is like K-Swiss or something like that. CHARLES: It's got to be some defunct brand. ARASH: BK Knights. JEFFREY: Mosaic is the LA Lights. CHARLES: Those were great. JEFFREY: So once I have this design, I'm starting to move to code and I'm starting to build some UI, how can I iterate on my API from there? Because I'm starting to actually build a real app, I want to connect to something, I need a data store. What can I do there? CHARLES: We've talked about this a lot, I think on this podcast, really over the years. And this is a technique that we got from the Ember community. There's a stack of fantastic libraries. There's Pretender which allows you to stub out XMLHttpRequests using a DSL, kind of like Node Express. And then based on top of that, there's basically an entire fake API layer which allows you to build, I would say it's not even really a stub at this point. It's like actually a prototype server implemented entirely in your browser. It's called Mirage. JEFFREY: So, you think about it, almost like starting in Sketch and then going to HTML. You're starting in some pretty simple JavaScript and then you're working your way up to what that API design looks like. CHARLES: Right. And so that lets you experience all of the nuance of API designs. So it comes with like you can experiment with different serialization formats, what are my property's going to look like? You can experiment with how do I load related data? So, if I've got a list of users and I want to get all of the comments that they've ever posted on my site, you might want to load those at the same time. So whether your API's going to support that and how it's going to support that, you can't really know until you actually have a consumer of that API. So what Mirage lets you do is it lets you consume an API you haven't written yet and you get to feel what it's like on the client and you get to make changes to that interface at a very, very low cost. So there's no deployed infrastructure, there's no automatically generated documentation. There's no real consumers yet. There's no multiple clusters running in the Cloud and it's very, very, very lightweight. It's just running right there in the browser. And so what that lets you do is if you have an insight about the shape of the API, it lets you validate that insight. Or if you have an assumption that you have about your API that actually is going to be detrimental to your experience, you get to have that assumption invalidated very quickly. And so at the backend of this process, you end up with a backend that is optimally shaped to serve the experience that you're shooting for. ARASH: So once you've got that, how do you reconcile it against is this a good API that I want to expose externally because maybe it's not. CHARLES: Like what do you mean? ARASH: Imagine that we've built the UI and we've iterated on the API in a fake stubbed way with Mirage or some similar tool and we've got to a state that we're pretty happy with, with the API design that works for this UI. Now, imagine we want that API to also be available to other things. CHARLES: Right. ARASH: How do we reconcile that? CHARLES: That's actually, I think that's kind of an open question right now, right? I mean, we don't really have a good answer to it because it is a stubbed API. And ultimately you're going to have a real API. So at some point, you do have to say like, this is the shape that I want. I'm going to go ahead and create these things and I need to make sure that those two APIs actually line up. Is that what you're asking is like, how do I make sure that they line up? ARASH: Sure. That's one piece of it. CHARLES: Oh, that's one piece of it. OK, so this is actually...we'll explore this process. This is actually like a problem, I think, with the stubbed approach is you have your set of stubs and then you have kind of the real McCoy which eventually will come along. So, it's great to have a server running inside the browser, but at some point you're going to need an actual server that's running in the Cloud. ARASH: Will you? Like what does the future hold? CHARLES: I mean, yes because the data needs to move, right? The data needs to move off your laptop. Honestly, Arash asked a good point if you're making an offline application. So if you're making an offline application, this actually allows you to bring a persistence architecture to the browser that is like every other... you don't have to make a special one off case. You can treat your backend like a backend. It's just running on the frontend. So that's probably a corner case, but it's worth pointing out that there used to be like back in the day, if you're using something like Microsoft Word or Excel or some other offline app, you can go a long way without having any internet connectivity, but you get to build it in exactly the same way. And then when you are ready to have internet connectivity, you've got the architecture in place. So, the future might not hold that and you might actually be able to use this in production. I would say it's a minority of cases. Most time you actually are going to want to have a server component. Let's say that you do, now you've got your real API and then you've got your prototype API that you run your tests against or that you're running against, and they need to line up because your frontend is going to be using both of them kind of throughout the development process. So there are a couple of strategies to deal with this. I'd say one is you run automated tests against both versions and that's a whole another subject of having testable APIs. Like most APIs that we have that we develop aren't set up to do end to end testing including a lot of the ones that we've written, although I think going forward now that we have a better handle on it, we can do that. We can definitely unpack that subject at some later point like making testable APIs. But I would say that the other strategy that you can use is use some sort of third party verification mechanism where you essentially record a bunch of interactions between your application and the fake API. And then you take those recorded applications and have them in some sort of repository and you can play them back on your real API and make sure that the responses generated by your real API for those recorded interactions to match up. So it's kind of like, I don't know, it's just a machine to make sure that the APIs stay in sync. ARASH: That's a domain that we need to get better at. CHARLES: Yeah. ARASH: We're only scratching the surface there. CHARLES: We're definitely only scratching the surface there. But the power of being able to develop without a real API first is enough so I think it makes the exploration warranted. There are some established tools in this space. The biggest one that I know of is called Pact. It's both a library and a repository. So it's kind of like got a...I don't know if there's a central server for it, but it's kind you record interactions, you upload them to a Pact server and then you can verify. So you can actually have a lot of consumers. And so, it's designed not only for making sure that your stubbed API works, but it's also for making sure that you just don't make breaking API changes. You can actually collect a lot of data about how people are using your API and then you can use that as a repository for when you make a change in your API to verify that'll work for all these other people. So if I'm just some random person or some random developer using your API, I can...kind of like how you record [inaudible] statistics and stuff to make the Apple experience better or whatever. It's very common for developers to ask, to record for certain anonymous data. You can submit anonymous data in the form of like Pacts. And so that can help an API developer verify whether the change they're going to make is going to break clients out there. So that's a little bit of a sidetrack there, but it's something that you start to think about a lot more when you start to develop in this fashion. ARASH: Did you feel like Outside-In development is a timeless approach to software development? CHARLES: I do. I feel like Outside-In, it actually even pervades more of software development than actually like the building the software. Like I feel that the longer you go in software development, you realize that the highest value activity is to front load understanding. So whether you're submitting a pull request, whether you're working on a work ticket, whether you're documenting code or even writing a method, the highest value activity that you can be engaged in, in each one of those points is understanding what the hell you're doing. ARASH: And why, too. Right? CHARLES: Yeah, exactly. Why? Understanding the motivation. What's your prime directive? What is the context on which you're entering into this piece of work? JEFFREY: I'm going to go with a bit of a contrarian approach. CHARLES: OK. JEFFREY: I'm going to go with a "maybe"... CHARLES: Maybe? JEFFREY: Maybe this is timeless. CHARLES: Maybe it's timeless? JEFFREY: Because I think historically, so much of software development was working with constraints. And the particular types of software that we're working on, the most important constraints are on the frontend. What does the end-user experience look like? But historically, that hasn't been the case. Historically, the primary constraints have been what can this technology stack that I'm working on actually do? CHARLES: Like what is the computer experience that I can support. JEFFREY: Yeah. And so that was actually the bulk of the work was like how can I actually get something that I want out of this giant machine in a room with me? So, maybe it is timeless, maybe not. But I think it is the way going forward. CHARLES: OK. So I agree that there's an interplay. There is kind of a yin and yang cycle. And I don't mean the cycle of we go to where we have to think about this and then we go to where we have to think about that. But I take your point, Jeffrey, but I think of something like Super Mario Brothers, which is I would say both a miracle of experience but also a miracle of technology in the sense that I think it was hand coded in Assembler on an 8-bit controller with who knows how much memory, the whole thing. So taking that into account, they had to think very strongly about what the computer could do at that point. They were operating under some just incredible constraints. But at the same time, they were thinking about what...they very clearly were focused on what is the coolest game that we can make at this point. So you're absolutely right. You have to hold both inside your head. You don't want to go crazy. I mean, we could sit down on the Balsamiq thing and be like, the first thing we're going to do is we want a VR room with...okay, no. Let's dial it back. JEFFREY: How do you wireframe VR? I've never seen anybody try do that. CHARLES: The Frontside Podcast episode 97: Wireframing VR. JEFFREY: Interesting. CHARLES: How we wireframe VR. So yeah. I agree. I take your point. You do have to hold both in your head at the same time. But I would say start with one a little bit and then see where that can take you, that the task of gaining understanding about what you're trying to build [inaudible]. JEFFREY: Yeah. CHARLES: If you try to understand what you're trying to accomplish, then you can try to push the tech stack towards that direction and maybe push a little progress forward. And then if you've accomplished something that you couldn't accomplish before, then you can start dreaming about even better experiences. And so kind of moving...like the wheels on He-Man's magic bus or whatever. JEFFREY: This is out of my domain. ARASH: I'm so [inaudible] backwards right now. JEFFREY: Our references are not timeless. CHARLES: Haven't you seen the...what's the one where he's like singing the song like the 4 Non Blondes song? And I said, hey, yeah, yeah. You haven't seen the He-Man, like the cover of 4 Non Blondes? ARASH: Oh, like they dubbed his... CHARLES: Yeah, no one's seen it? Oh, man. ARASH: It's starting to sound familiar. CHARLES: OK. I mean, this is like we're talking... ARASH: This is like 2006 internet? CHARLES: No, this is like 2010 internet. It's not the ancient past here. ARASH: I'm going through my internet filing cabinet in my brain right now. CHARLES: Okay. It had particular significance because the friends from attorney were also part of my childhood and I realized I'm unique in that aspect. But they basically, in those days they had the Hanna-Barbera cartoons were very cookie cutter, so they basically took the Mystery Machine from Scooby-Doo and they kind of re-colored it and they put like weird tank treads that like they put really funky kind of weird futuristic He-Man wheels on it. And it went from the Mystery Machine to He-Man's kind of a ride. ARASH: They repurposed all the illustrations. CHARLES: Exactly. Hey, you got to save time. ARASH: Save time somewhere. CHARLES: Doing your framework. ARASH: Kids need cartoons. CHARLES: That's right. So anyway, that's how the wheels on He-Man's Mystery Machine worked. ARASH: This has been interesting for me because when we first started this conversation, we're looking at it as Outside-In development. But we've talked so much here about design and creation that it almost starts to feel like Outside-In development is almost too narrow. Like it's really what we're talking about here is Outside-In creation of anything useful and valuable to people. CHARLES: Yeah. It's easy to overlook like whenever you want to create something, you get so focused on the actual building of it or the making of it happen that you kind of lose sight of where it is that you're going. And I think that sometimes it's important to be able to create without knowing where you're going to kind of push the paint around the canvas, so to speak. I think that's a valuable activity, like sometimes it's important to just code without really having any clear direction. You're just kind of following your instincts. Then it's the same way you look at Picasso's study in charcoal or whatever. There'll be like a picture of a horse leg and Picasso's like, "Oh, there's a horse leg. Man, how do I capture a horse leg?" And not really having much intent. And so that's important. But I think when you're building systems or you're creating something that you want to have a real lasting impact, you do need to consider it holistically and you really need to understand why it is that you're doing what you're doing. JEFFREY: Part of what's awesome about working in software is that unlike Picasso who had to start a new piece, we can keep working on the same piece and be able to paint over it multiple times. And you can start with that outline of like, "Hey, this is the vision that we see this particular thing going." But then don't make space for like, "Let's just push the paint around and see what happens in this little section," and that's fine. CHARLES: Yeah. And I think that because software is so malleable that it can end up capturing a lot of what is typically considered design. I think this has kind of also been a theme that we've talked about kind of over the last year or so is that over the last 20 years we've kind of seen software capture a lot of what were once separate practices. So when I was first starting out, it was quality. The line between QA and development was very stark certainly at the beginning of my career. And there was a fusion that was happening right as I joined of QA and development. And we saw basically the testing revolution, realizing the testing needs to be brought into the center of development, which needs to be put forth first if you want to have quality, be something that you want. And then, a revolution that I saw kind of in the middle of my career is seeing operations. It used to be certainly for many years into the beginning of my career, like the people who maintain the software were very different from the people who wrote it and there was a big divide there. And with the Dev Ops movement, it's kind of the realization that no, if we want to have healthy operations, we need to understand what healthy operations are at the very beginning and we need to like put them at the beginning of the process. And I think that what we're seeing now, maybe a revolution that hasn't quite happened yet, but we're on the cusp of is seeing design burrow its way to the heart of development where it's like we want something to be beautiful. We want it to be frictionless. We want it to be delightful to its end users. It needs to be there from the get go and developers need to be thinking about it. It's not someone else's responsibility. It's you as the primary creator. JEFFREY: It doesn't matter how elegant of an API you've created if the end user experience is just not there. CHARLES: Yeah. So it's all about tearing down. There's been a series of walls that have come down that I've witnessed. And so I think this is one that's in the process of crumbling. ARASH: So, this has been an awesome talk. How would you summarize Outside-In development and what it means to Frontside today and in the future? CHARLES: I think that it really is about making sure that the understanding is solid. That's the core piece, frontloading understanding, realized through a stack of tools. So the tools we use are some sketch and design tool. We'll sketch out the idea we really like, ask questions and try and understand it and firm up in our idea, like have a vision of what the experience is going to be like. Then the next step is to write some acceptance tests. So to define done, define what your criteria are going to be so that if I run these automated tests, the code will in fact realize the experience that I'm dreaming about. To do that, we've actually been assembling a suite of tools over the past year to do that and we've actually started releasing them to the world. So, it's still in a...I don't want to say alpha because we're using them in production systems, but it's much more of a work bench at this point than a framework, if that makes any sense. So we have about four related tools under the big test tent. We have interaction library for stubbing out, gestures, mouse clicks, keyboard events, scrolling. We have assertion library that works with any other source. It's really an assertion extension or extension wrappers to make your assertions impervious to asynchrony. We've extracted Mirage from Ember CLI Mirage so that you can use it in any project, React, Vue, Ember, what have you. You can check it out at big test. It is for early adopters right now, but it is in production systems and if you want to acceptance test anything, command line, back client, what have you, if you're willing to write some JavaScript, you can write those acceptance tests and have them be robust. And whatever experience you're trying to create, you can validate it with that. And so, that's why we created it. JEFFREY: And that's really a good marker of where we are in our experience with Outside-In development right now is we've been doing this in practice for awhile at this point and we're crafting tools to help us be even better at it and sharing those. CHARLES: Right. And so we're pretty excited about these tools because I think they bring solutions to a lot of the problems you're going to encounter. So there's a lot more work to do and we're excited to do it. Head on, check those out. And we'll go ahead and wrap up. Just a few quick announcements. If you're going to be at Assert(js) tomorrow, the Frontside is going to be there. I'm going to be there. Mr. Wil Wilsman is going to be there. So if you're there, please do give us a shout and we'll hang out. And then on the next podcast, we are really, really excited. I'm both nervous and I just can't keep a lid on it. We're going to have Erich Gamma on the podcast to talk about the language server protocol that he's been working on. If you don't know Erich Gamma, he's one of the Gang of Four that wrote The Design Patterns Book. He was the primary architect behind Eclipse and most lately VS Code. So, if you've used any of those projects or benefited from them, which I have benefited immensely from all three, it's going to be really, really exciting. So, that's something to look forward to. And with that, I will say goodbye to you, Jeffrey. JEFFREY: Ciao! CHARLES: And to you, Arash. ARASH: Adios! CHARLES: And everybody listening along at home or in your cars or cleaning your kitchen as I do when you listen to podcasts, we'll see you next time. If you want to get in touch with us, you can always give us a shout on Twitter, we're @thefrontside or you can drop us a line, contact@frontside.io.

Joey Kissimmee says that he's not techy, but he has created iPhone apps, SaaS products, WordPress themes, and is now working on WordPress plugins. He says that he has always been a hard worker. His first job was washing dishes in a beat up old sandwich shop in Chicago when he was twelve. In 2000, he started working at Walmart and doing a little business online to make some extra money to have fun with his wife and kids. “At first,” he says, “it was just selling junk on eBay.” But he found some mentors, he listened, he learned, and he implemented the things he learned. He created a few tools that he couldn't find and then turned these tools into products. Somewhere around 2008 or 2009, he realized he was making some pretty good money from his online business and decided to take it seriously. By early 2010, he was able to retire from his job at Walmart to work his online business full-time. Please see Disclosure* (below) concerning affiliate links on this page. Key Segments [03:00] Joey is not a developer, so how did he get into the SaaS world? He says he's not techy. Joey wasn't even sure what SaaS meant until long after he was creating SaaS products. [03:55] He didn't set out to become an entrepreneur; he just wanted to sell some junk on eBay. [04:25] When he first started to get involved with marketing, his mentors were creating little tools to perform tasks. [05:05] He started creating iPhone apps in 2011, and that's where he really learned to hire people to create things. [06:25] Anything he had to do repeatedly, he would pay someone to automate for him. He systematized his processes and created tools for himself. [07:00] In about 2010 a buddy in the affiliate marketing world told him: “Dude, you could sell this stuff.” [07:40] He was a good listener, and he took action. He just implemented what worked. He created TubeSlicer.com as a tool to do the five things he knew how to do with Photoshop for creating YouTube thumbnails and then turned this into a product. He did the same thing to create Image Ad Creator a product to create images for split testing Facebook ads. [09:15] Every product he created was to solve his own problems, and then he figured out a way to turn it into a viable product. He created Tube Slicer, Image Ad Creator, TimelineSlicer, and Podcast Artwork Slicer out of his own needs. Appendipity, his premium WordPress theme, was created the same way and turned into a huge success. [10:00] “I don't care who says what, outsourcing is an art form.” When you're outsourcing you don't have to know coding, you have to know the lingo. [11:30] Rule #1: Know how you want to use the product. The coder doesn't really care about or understand the Ux (user experience). Your problems aren't unique. There's a good chance that a dozen other people have the same problem; so if you can figure out how to solve it for yourself, you just solved it for a dozen other people. [12:14] Rule #2: Know the lingo. [13:00] To communicate Ux to the designer for his WordPress designers he draws on a legal pad and then scans it and sends it to them. For iPhone apps, he used Balsamiq to do wireframes. 14:30 Once it's working the way you want it to work, fiddle around with the look of it. Once the mock-up's done and you've got a working prototype, send it to the designer. [16:00] His go-to place for designers was oDesk. He also used Freelancer and eLance. (Note: oDesk and eLance merged in 2015 and formed Upwork.) [16:40] You could get hosed in many ways. The developer and the designer could overcharge you. People could also steal your ideas. One way Joey protected himself was not to give too much information on the job posting. [17:00] Joey gives an example of how he does a job posting and then explains his filtering process for hiring. [18:50] Once he has filtered out the best candidates, he shares more detail privately with them. If he has a good feeling about an individual, he does a live Skype session with them. You have to trust your gut. No matter how qualified someone may seem, if you don't feel right about it, and there's just something off, forget it. [21:55] For design work, he now goes to 99designs but uses a slightly different process because of their crowd-sourcing-like model. [23:00] Now, he can also put the word out to his email list that he needs people and use a survey on Google Forms to collect responses. Requirements are in a question format. He doesn't use a code word in these surveys, but the rest of the process is the same. [24:50] Joey has developed four different types of software products but uses one well-refined process to find people in all cases. Joey picked these things up by paying attention, listening, being connected to a few good people, and doing it. [27:40] Joey recommends The 4-Hour Workweek, The ONE Thing, and Influencer (see Resources Mentioned below for additional details). [29:00] Joey takes the end of one year and beginning of the next to spend with his family and to reflect on his business. He reflects on how things have gone in the past year and what he might want to try in the next. [32:15] He is fortunate to be able to take himself out of the equation. He learned to create evergreen businesses that don't need his name or his face to make money. Create brands that can stand on their own. [35:15] Don't become brand dependent. Don't become the brand because you won't make any money if you take yourself out of the equation. Build the product as the brand. [35:45] You can create a SaaS product, and you don't have to be the actual product. Be behind the scenes. Let the product breathe. Build the product into a brand. Make it the best thing possible. [36:55] You don't have to make it the best thing possible at the beginning. The beauty of SaaS is the ability to release versions. Build a working prototype, release it for free or dirt cheap, and then get feedback from the customers. Let the customers build the features into it then package it up, raise the price, and sell it. People will buy it because it's customer driven. They built the product. [38:20] You will get a lot of crazy requests from guys who think so far outside the box, they lose the box. Filter by the majority of requests. [41:15] “You just gotta go out there and do it. I always tell people, and I preach this off the rooftops: ‘You must listen. It doesn't matter where you're listening from. You have to listen to everything that they say. Learn as much as you can. There's no possible way you can learn everything that they say and jot everything down. Just jot down and take mental notes of the things that resonate with you. Then when you're done listening and learning, go out there and implement it. That's the freakin' key thing right there. If you don't implement, if you don't take action, the only guaranteed results to zero is if you do nothing. You might as well do something. If you're gonna get zero anyway by doing nothing, you might as well go ahead and try to do something so you'll get some kind of result.'” [42:05] “Do something. That's the way I go about it. You know, hey, it's gonna be zero anyway if I do nothing. So I might as well get a zero by doing something. ‘Cause at least, I gave it a whirl.” [42:55] “If you can use your own product, you've got something good to share with people.” Resources Mentioned 99designs – web-based service for design freelancers. Appendipity – premium WordPress theme created by Joey Kissimmee. Appendipity is particularly well-suited to podcasting. This site uses Appendipity. Balsamiq – wireframing app. Freelancer – web-based service for freelancers of all kinds. Google Forms – online form app from Google. Results transfer into a spreadsheet. Image Ad Creator – app created by Joey Kissimmee “that allows you to create beautiful and professional looking image ads to use with your Facebook advertising.” IncomePress.com – Joey Kissimmee's primary personal website and podcast. Influencer: The New Science of Leading Change, Second Edition – book by Joseph Grenny, Kerry Patterson, David Maxfield, Ron McMillan, and Al Switzler about making change happen. Photoshop – SaaS for processing images. Podcast Artwork Slicer (server move in progress) – product by Joey Kissimmee to create inexpensive album artwork for iTunes. The 4-Hour Workweek – book by Tim Ferriss free yourself from as many tasks as you can so that you can live differently, doing only the things that you alone can do. The ONE Thing: The Surprisingly Simple Truth Behind Extraordinary Results – book by Gary Keller and Jay Papasan describing a simple, powerful concept to focus on what matters most. TimelineSlicer (server move in progress) – app created by Joey Kissimmee to “create custom cover photos for your Facebook Timeline.” TubeSlicer.com (server move in progress) – app created be Joe Kissimmee to create thumbnails for YouTube videos Upwork – web-based freelancers of all kinds. *Disclosure: Some of the links on this page may be affiliate links. I may earn a commission if you purchase through these links. These commissions help to cover the cost of producing the podcast. I am affiliated only with companies I know and trust to deliver what you need. In most cases, affiliate links are to products and services I currently use or have used in the past. I would not recommend these resources if I did not sincerely believe that they would help you. I value you as a visitor/customer far more than any small commission I might earn from recommending a product or service. I recommend many more resources with which I am not affiliated than affiliated. In most cases where there is an affiliation, I will note it, but affiliations come and go, and the notes may not keep up.

Peldi Guilizzoni is the founder of Balsamiq Studios, which makes Balsamiq Mockups a tool for creating quick and intuitive user interface mockups. Peldi launched Balsamiq as a one-man software company in 2008 and within 18 months, Balsamiq reached $2 million in revenue. Balsamiq is on track this year to hit $6 million in revenue. Links & Resources Mentioned Balsamiq Adobe Enjoyed this episode? Subscribe to the podcast Leave a rating and review Follow Omer on Twitter Need help with your SaaS? Join SaaS Club Plus: our membership and community for new and early-stage SaaS founders. Join and get training & support. Join SaaS Club Launch: a 12-week group coaching program to help you get your SaaS from zero to your first $10K revenue. Apply for SaaS Club Accelerate: If you'd like to work directly with Omer 1:1, then request a free strategy session.