<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Raúl González on Medium]]></title>
        <description><![CDATA[Stories by Raúl González on Medium]]></description>
        <link>https://medium.com/@Raulgzm?source=rss-71d55c8ad440------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6mKenIdS0eR8UVNTggenTg.jpeg</url>
            <title>Stories by Raúl González on Medium</title>
            <link>https://medium.com/@Raulgzm?source=rss-71d55c8ad440------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 00:34:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Raulgzm/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Aligning Tech with Business Goals: A Guide for Startup Founders]]></title>
            <link>https://medium.com/@Raulgzm/aligning-tech-with-business-goals-a-guide-for-startup-founders-0904157370ff?source=rss-71d55c8ad440------2</link>
            <guid isPermaLink="false">https://medium.com/p/0904157370ff</guid>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Raúl González]]></dc:creator>
            <pubDate>Thu, 14 Nov 2024 12:10:45 GMT</pubDate>
            <atom:updated>2024-11-14T12:10:45.766Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Aligning tech strategy with business goals is crucial for startup success.</blockquote><blockquote>This guide outlines practical steps that help founders focus on tech initiatives driving growth and product-market fit.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ihnoIVhqmURq-EIwR-SAjg.png" /></figure><p>In the fast-paced world of startups, technology decisions can often feel overwhelming, especially for non-technical founders. With limited resources and constant pressure to find the right market, it’s tempting to choose tech solutions based solely on cost or immediate needs. But here’s the truth: <strong>aligning your technology choices with your business goals is one of the most powerful ways to accelerate your startup’s growth.</strong></p><p>This guide is designed to help startup founders understand the importance of tech-business alignment and provides practical steps to ensure every technology decision supports growth, improves efficiency, and ultimately drives revenue. For early-stage companies, especially those without a technical co-founder, the ability to make strategic tech choices that contribute directly to business objectives can be the difference between fast growth and a series of costly mistakes.</p><p>Without alignment between tech and business strategy, startups risk investing in solutions that don’t move the needle. The right tech investments not only save money but also lay a scalable foundation for future growth. When tech and business objectives are synced, every dollar and every decision works toward the same goals, creating a streamlined path to success. By the end of this article, you’ll have a clear framework for identifying and prioritizing tech initiatives that drive your startup forward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2MfuNyOC8bPMxZuNvysMVA.jpeg" /></figure><blockquote>Without alignment between tech and business strategy, startups risk investing in solutions that don’t move the needle.</blockquote><h3>Technology as an Enabler, Not a Cost</h3><p>For many startup founders, especially those without a technical background, technology can seem like a necessary but burdensome expense. Yet, this mindset misses the true potential that tech holds: technology, when strategically aligned with your business goals, becomes a powerful enabler of growth rather than just a cost. By leveraging the right tools and systems, startups can accelerate their path to product-market fit, adapt more quickly to customer needs, and scale more effectively.</p><p>In Jim Collins’ book Good to Great, <strong>technology is described as an “accelerator” rather than the main driver of greatness</strong>. In other words, tech doesn’t create success on its own; instead, it’s the strategic use of technology that drives momentum, amplifies your strengths, and helps your company achieve its goals faster. This principle is especially valuable for startups, where tech decisions must be carefully aligned with the core mission and objectives to make the most of limited resources.</p><blockquote>Tech doesn’t create success on its own; instead, it’s the strategic use of technology that drives momentum, amplifies your strengths, and helps your company achieve its goals faster.</blockquote><h3>Business Goals Supported by Tech</h3><p>Every tech decision should be directly linked to supporting your business objectives. Here are some common goals for early-stage startups and how tech can help achieve them:</p><h4><strong>Acquiring Users</strong></h4><p>User acquisition is often a top priority, and technology plays a crucial role in reaching and engaging new customers. Whether it’s through digital marketing tools, analytics platforms, or a customer relationship management (CRM) system, tech solutions can provide insights into where your users are, how they’re interacting with your brand, and what draws them to your product.</p><p>User acquisition is a top priority for startups, and technology is a crucial enabler in reaching, engaging, and converting new customers. One of the most effective ways to increase acquisition is through optimizing landing pages and digital ads to ensure they resonate with the target audience. By using A/B testing tools, startups can experiment with different headlines, visuals, and calls-to-action on landing pages to determine what drives the highest conversions.</p><p><strong>Language-market fit</strong> is also essential here. This means refining the messaging in ads and on landing pages so that it speaks directly to the needs and pain points of the target users. Tools like analytics and heatmapping software can provide insights into how users interact with the page, highlighting which messages or visuals engage them most effectively. By continuously aligning the language and positioning to the market’s needs, startups can create a clear, compelling path to conversion.</p><p>With data-driven improvements to landing pages and ad content, startups can optimize user acquisition campaigns, ensuring that they reach the right audience with the right message. This tailored approach ultimately increases the likelihood of capturing interest, driving clicks, and converting new users into engaged customers.</p><h4><strong>Improving Activation</strong></h4><p>Activation refers to the moment when a new user experiences the core value of your product for the first time. To increase activation rates, tech can help streamline onboarding, personalize the initial experience, and guide users to value quickly. For instance, user analytics tools can highlight where users drop off in the onboarding flow, while automated in-app messaging or tutorials can help new users overcome any initial hurdles. By leveraging these tools, startups can optimize the user journey, improving the likelihood that new users become active, engaged customers.</p><h4><strong>Improving Retention</strong></h4><p>Retaining customers is key to sustainable growth. Product and customer analytics tools allow startups to track user behavior, identify areas for improvement, and personalize the user experience. Retention-focused technology, such as customer feedback tools, automated communication platforms, and in-app engagement features, can help keep users satisfied and loyal.</p><h4><strong>Increasing Operational Efficiency</strong></h4><p>For startups, efficient operations can be the difference between scaling successfully and becoming overwhelmed by growth. Implementing automation tools, project management software, and collaborative platforms helps streamline workflows and allows your team to focus on high-value activities. This increased efficiency ultimately supports faster growth by freeing up resources and reducing time spent on manual processes.</p><h4>Real-world Example</h4><p>Consider a startup focused on a mobile app for personal finance. Their main goals are acquiring users, improving retention, and scaling efficiently to keep up with demand. Initially, the founders saw technology as a cost to minimize, opting for basic tools and infrastructure. However, after implementing a customer data platform (CDP) that tracked user engagement, they discovered valuable insights: users were dropping off after a particular feature.</p><p>Armed with this data, they improved the feature and added a tutorial based on real user behavior. Additionally, by integrating marketing automation tools, they re-engaged these users with targeted email campaigns. The result? User retention improved by 30%, and acquisition costs decreased by 15% as their messaging became more relevant to prospective users.</p><p>In this case, technology acted as an enabler, providing crucial insights and capabilities that would have been impossible to achieve with manual methods alone. Rather than seeing tech as a cost, the startup leveraged it to address specific business goals, accelerating growth and enhancing user engagement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*irOIFPIwpn5n6G54.png" /></figure><h3>Key Steps to Align Technology with Business Objectives</h3><h4><strong>Step 1: Identify Core Business Goals</strong></h4><p>Before making any technology decisions, it’s crucial for startup founders to clearly define their core business goals. Each tech investment should directly support a business objective, such as improving customer experience, increasing operational efficiency, or boosting user retention. By aligning tech initiatives with these goals, startups can ensure that every investment works to accelerate growth, improve user satisfaction, or enhance internal productivity.</p><p>For early-stage startups, resources are often limited. This means every tech investment should be purposeful and directly connected to a specific business objective.</p><p><strong>Framework to Articulate Business Goals:</strong></p><p>To help founders clarify their business goals and connect them to tech investments, consider using this simple framework:</p><ul><li><strong>Define Your Primary Business Objective(s)</strong>:<br>- <strong>Ask</strong>: <em>“What is our top priority right now?”</em><br>- <strong>Examples</strong>: acquiring new users, retaining current users, or reducing operational costs. This is where you define the outcome you want technology to help achieve.</li><li><strong>Identify How Technology Can Support These Objectives:<br>- Ask</strong>: <em>“Which specific tech tools or systems can help us achieve this goal more effectively?”</em><br>- <strong>For example</strong>, if your primary goal is improving customer experience, consider tech solutions that enhance user interactions, like chatbots for customer support or personalization engines for tailored content.</li><li><strong>Set Specific, Measurable Targets:<br>- Ask</strong>: <em>“What does success look like in numbers?”<br>- </em>Define specific metrics tied to each goal, like a 20% increase in customer retention or reducing response time by 30%. These metrics will help you assess the effectiveness of each tech investment.</li><li><strong>Evaluate Feasibility and Prioritize:<br>- Ask</strong>: <em>“Which tech initiatives are most feasible and impactful right now?”<br>- </em>For startups, not all investments are immediately feasible. Rank tech initiatives by impact and feasibility, focusing on those that directly advance your business goals and can be implemented with available resources.</li></ul><p>By using this framework, founders can make informed technology decisions that align closely with their startup’s most pressing business objectives, ensuring each tech investment supports their broader growth strategy.</p><h4><strong>Step 2: Map Tech Initiatives to Business Goals</strong></h4><p>Once you’ve identified your core business goals, the next step is to map specific tech initiatives to each goal. Every tech investment should have a clear and measurable impact on a particular business objective — whether that’s improving customer experience, increasing operational efficiency, enhancing user engagement, or enabling scalability. By aligning each tech solution with a business outcome, you ensure that technology decisions are purposeful and support the startup’s overall growth strategy.</p><p>Mapping tech initiatives to business goals helps keep resource allocation focused, making sure that each tech investment contributes to measurable results. This approach minimizes wasteful spending and aligns your tech stack with the most pressing business needs, accelerating your path to achieving product-market fit, retaining users, and scaling sustainably.</p><p>Here’s a table that illustrates how various tech initiatives align with common business goals:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L4ROCVDwIVUlt_96FjQcXA.png" /></figure><p><strong>How to Use This Mapping Approach</strong></p><ol><li><strong>Set Clear Objectives for Each Tech Initiative:</strong> Determine how each tool or platform will support a specific business goal. For example, if improving customer retention is a priority, investing in a product analytics system should directly help you understand where users drop off and enable you to optimize accordingly.</li><li><strong>Prioritize Tech Investments Based on Impact</strong>: Identify which tech solutions will have the most immediate and significant impact on your business objectives. For a rapidly growing startup, investing in scalable infrastructure may take precedence, while a company focused on improving customer retention might prioritize product analytics.</li><li><strong>Measure and Iterate</strong>: After implementing a tech solution, track the key performance indicators (KPIs) associated with the relevant business goal. Regularly review these metrics to determine whether the tech initiative is meeting expectations and delivering value.</li></ol><p>By mapping each tech initiative to a specific business goal, you build a cohesive strategy that ensures every technology investment is meaningful. This approach allows startup founders to make strategic, data-driven tech choices that deliver measurable business impact, supporting both immediate objectives and long-term growth.</p><h4><strong>Step 3: Prioritize High-Impact Tech Projects</strong></h4><p>For early-stage startups with limited resources, not all tech initiatives will deliver the same impact. Prioritization is crucial to focus time, energy, and budget on the projects that will drive the most meaningful growth. By evaluating tech projects based on their potential impact and resource requirements, startups can ensure that each decision contributes to core business objectives and maximizes the return on investment.</p><p>As a startup, the resources — both time and budget — you can allocate to tech initiatives are often constrained. Prioritizing high-impact projects helps avoid spreading resources too thin and ensures that each tech investment brings you closer to your goals. Without prioritization, startups risk investing in low-impact projects that may consume resources without delivering significant value.</p><p><strong>Introducing a Prioritization Framework:</strong></p><p>To effectively rank tech initiatives, use a prioritization framework that assesses each project’s potential impact, cost, and effort. Two popular frameworks for prioritizing projects are the ICE Score and MOSCOW method. Let’s break down each framework:</p><p><strong>ICE Score (Impact, Confidence, Effort)</strong></p><p>The ICE Score is a straightforward framework for evaluating projects based on three criteria: Impact, Cost, and Effort. By scoring each project on these metrics, you can quickly identify which tech initiatives are likely to bring the highest value with the least resources.</p><ul><li><strong>Impact</strong>: How significantly will this project contribute to your business goals? For example, will it improve customer retention, boost revenue, or increase operational efficiency?</li><li><strong>Confidence</strong>: How certain are you that this project will deliver the expected results? Confidence scores are often based on previous experience, industry data, or user feedback. Higher confidence scores mean there’s strong evidence or a clear rationale supporting the initiative’s success.</li><li><strong>Effort</strong>: How much time, manpower, and resources will be needed to complete this project? Projects with lower effort can be easier to tackle quickly, delivering faster results.</li></ul><p>Higher scores indicate higher priority, guiding startups to focus on initiatives that will have the most impact relative to their cost and effort.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/737/0*KU3rCe5FBzDrTPG_.png" /></figure><p><strong>MOSCOW Method (Must-Have, Should-Have, Could-Have, Won’t-Have)</strong></p><p>The MOSCOW method helps categorize projects based on necessity and urgency, making it particularly useful for early-stage startups where focus is key.</p><ul><li><strong>Must-Have</strong>: These are essential projects that directly support critical business goals and have a significant impact. For example, setting up a scalable infrastructure might be a must-have for a startup preparing for rapid growth.</li><li><strong>Should-Have</strong>: Important projects that add value and support growth but may not be essential in the immediate term. Implementing customer feedback tools could be a “should-have” if retention is a secondary priority.</li><li><strong>Could-Have</strong>: These projects are beneficial but not immediately necessary. They may enhance user experience or improve team efficiency, but they aren’t urgent.</li><li><strong>Won’t-Have</strong>: Projects that are either low-impact or don’t align with current goals. These can be set aside to focus on higher-impact initiatives.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cQp5Rff9yZ6pswiJ" /></figure><p>With this categorization, founders can concentrate on “must-have” initiatives first, ensuring that essential projects are addressed before allocating resources to secondary or optional ones.</p><h3>Common Pitfalls to Avoid</h3><p>When aligning technology with business goals, it’s easy to fall into certain traps that can derail progress and waste valuable resources. Here are some common pitfalls that early-stage startups should avoid to ensure that their tech initiatives effectively support their growth objectives.</p><h4><strong>Misalignment with Customer Needs</strong></h4><p>A common mistake in early tech decisions is failing to prioritize features or initiatives that resonate with actual customer needs. Technology should ultimately serve your users by solving their pain points or enhancing their experience. Investing in tech that doesn’t align with customer needs or expectations can result in a product that feels out of touch, leading to low engagement or even churn. Use customer feedback, behavior analytics, and market research to ensure that your tech decisions directly improve the user experience and address real customer pain points.</p><h4><strong>Overinvestment in Non-Essential Tech — Overengineering</strong></h4><p>For startups, every dollar and hour spent counts, and it’s tempting to invest in the latest technology or build complex systems that may not be essential. Overengineering — investing in features or infrastructure beyond what’s needed — can lead to resource drain without adding real value. Avoid the tendency to overinvest by focusing on the minimum viable technology required to achieve your core business objectives. Ensure that each tech investment directly supports a critical goal and resist the urge to build overly complex solutions too early.</p><h4><strong>Ignoring Scalability</strong></h4><p>While it’s crucial not to overinvest in tech, it’s equally dangerous to ignore scalability altogether. Startups often start small but need to plan for rapid growth, especially if product-market fit is achieved quickly. Implementing scalable infrastructure from the beginning — or at least laying the groundwork for it — helps avoid costly and time-consuming rework down the line. For instance, choosing a flexible cloud infrastructure allows for easy scaling as user traffic increases, making the business ready for growth without major disruptions.</p><h4><strong>Thinking About Performance Optimization Too Early</strong></h4><p>While performance optimization is important, focusing on it too early can lead to unnecessary complexity and resource consumption that detracts from more immediate business goals. In the early stages, the priority should be on building a minimum viable product (MVP) that provides value to users, not on optimizing every aspect for speed and efficiency. Prematurely investing in performance enhancements often results in overengineering, as developers spend time fine-tuning aspects of the product that may not yet impact user experience meaningfully.</p><p>Instead, aim for functional and user-focused performance, making sure the product works smoothly without diving into advanced optimizations. As your user base grows and you reach the limits of your existing infrastructure, you can then prioritize performance adjustments to scale effectively. This approach helps ensure that resources are invested in areas that directly support product development and market validation, rather than premature optimization that may not add immediate value.</p><h4><strong>Taking on Bad Technical Debt Hinders Fast Iteration</strong></h4><p>Technical debt is often unavoidable in the early stages of a startup, but taking on “bad” technical debt — making rushed or poorly planned technical decisions — can significantly slow down future development and limit your ability to iterate quickly. While some level of technical debt can be strategically managed, bad technical debt arises from cutting corners in ways that compromise code quality, scalability, or maintainability.</p><p>When tech debt accumulates without careful oversight, it creates roadblocks for future updates and feature releases, forcing developers to spend valuable time on fixes, rework, or untangling messy codebases. This slows down innovation and makes it difficult to adapt to new market needs or user feedback — key advantages for any agile startup.</p><p>To avoid this pitfall, focus on building a foundation of “good” technical debt that supports rapid iterations while allowing for flexibility and growth. Establish basic coding standards, document essential processes, and adopt a manageable approach to tech debt that allows you to build quickly without compromising future scalability.</p><p>Avoiding these common pitfalls will help ensure that your tech investments are purposeful, customer-focused, and scalable. By focusing on essential tech, planning for scalability, aligning with customer needs, maintaining a clear target audience, and refining your value proposition, your startup will be better positioned to achieve sustainable growth with a cohesive and effective tech strategy.</p><h3>Building a Culture of Alignment in the Team</h3><p>Building a culture of alignment within your team is essential for ensuring that technology initiatives truly support your startup’s business goals. By organizing teams effectively, fostering communication between tech and business functions, involving key stakeholders in tech decisions, and setting measurable goals, startups can create a cohesive and agile environment that drives meaningful results.</p><h4><strong>Team Organization: Cross-Functional Teams with End-to-End Responsibility</strong></h4><p>To keep tech initiatives aligned with business objectives, organize your teams around value flows — the key services or customer experiences that drive value for your users. This approach ensures that each team focuses on delivering specific outcomes that are directly tied to business goals, rather than isolated technical tasks.</p><ul><li><strong>Cross-Functional Teams</strong>: Cross-functional teams bring together individuals with diverse skills, such as developers, product managers, designers, and customer success specialists. This diversity helps ensure that the team can handle all aspects of a project and make decisions that benefit the user experience holistically.</li><li><strong>Value-Aligned Teams</strong>: Organize teams around specific customer-facing services or value streams, ensuring that they have a clear mission that aligns with the core business objectives. For example, a team focused on “user onboarding” can take end-to-end responsibility for the onboarding experience, from design and development to tracking user activation metrics.</li><li><strong>End-to-End Responsibility</strong>: Empower teams to take full ownership of their areas, from development through deployment to user feedback. When teams have end-to-end responsibility, they can make faster decisions, iterate based on user needs, and ensure their efforts align with overall business goals.</li></ul><p>This team structure reduces handoffs, encourages accountability, and allows each team to focus on adding tangible value to customers, keeping tech initiatives closely aligned with what matters most to the business.</p><h4>Embracing a Product Engineering Mindset</h4><p>Fostering a <strong>product engineering mindset</strong> within your team is essential for keeping tech initiatives aligned with both customer needs and business goals. Unlike a traditional engineering approach, which focuses mainly on technical requirements, a product engineering mindset emphasizes creating solutions that deliver real value to users and support the strategic objectives of the business. This mindset encourages engineers to think like product owners, understanding the “why” behind each feature and making decisions that prioritize user experience and business impact.</p><ul><li><strong>Customer-Centric Development</strong>: Engineers with a product mindset stay closely connected to customer feedback and behavior, ensuring that the features they build address actual user needs. This approach helps create products that resonate with the target market, ultimately enhancing user satisfaction and retention.</li><li><strong>Alignment with Business Goals</strong>: By understanding how each tech initiative supports broader business objectives — such as increasing retention, improving activation rates, or driving revenue — product-focused engineers make decisions that maximize business impact. For example, rather than building a feature for technical complexity, they’ll prioritize features that enhance the user journey or drive conversion.</li><li><strong>Ownership and Accountability</strong>: A product engineering mindset encourages teams to take ownership of both technical quality and product outcomes, from feature development through to customer impact. This fosters a culture of accountability, where engineers are not only responsible for the functionality of their code but also for its alignment with the business’s success metrics.</li></ul><p>Cultivating this mindset aligns the technical team with the startup’s mission and values, ensuring that every development effort is purposeful, user-focused, and strategically impactful.</p><h4><strong>Communication</strong></h4><p>Regular, transparent communication between teams is crucial for fostering alignment. Frequent touchpoints between these teams help ensure that tech decisions are always informed by business priorities and market needs.</p><ul><li><strong>Weekly or Biweekly Check-Ins</strong>: Schedule regular meetings where teams can discuss ongoing projects, share updates, and address challenges. This keeps everyone informed and prevents tech initiatives from diverging from business goals.</li><li><strong>Shared Language and Goals</strong>: Encourage a shared understanding between teams by aligning on common objectives and key metrics. This minimizes misunderstandings and enables both sides to work toward the same outcomes.</li><li><strong>Open Channels for Continuous Feedback</strong>: Use tools like Slack channels or project management platforms to facilitate ongoing communication, allowing team members to share insights, challenges, and adjustments in real-time.</li></ul><p>Effective communication builds trust and keeps everyone moving in the same direction, ensuring that tech efforts remain aligned with the strategic business vision.</p><h4><strong>Involve Key Stakeholders in Tech Decisions</strong></h4><p>For technology to effectively support business objectives, both business and technical stakeholders should be actively involved in major tech decisions. This collaborative approach ensures that each investment is evaluated from multiple perspectives, maximizing the likelihood that tech initiatives will drive measurable business impact.</p><ul><li><strong>Cross-Functional Decision-Making</strong>: When evaluating new tech investments or prioritizing projects, gather input from key stakeholders across departments. For example, product managers can provide insights into customer needs, while technical leads can assess feasibility and scalability.</li><li><strong>Business and Technical Alignment on Trade-Offs</strong>: Involving stakeholders helps balance technical and business priorities, particularly when deciding between fast delivery and long-term scalability. By jointly assessing these trade-offs, teams can make decisions that serve both immediate and strategic goals.</li><li><strong>Establishing Ownership</strong>: Ensure each stakeholder understands their role in the decision-making process and how their input contributes to the final outcome. This clarity fosters accountability and helps stakeholders stay invested in the success of tech initiatives.</li></ul><p>By involving both technical and business leaders in key decisions, startups can make more informed choices that align with both current needs and future objectives.</p><p>Building a culture of alignment in your team requires intentional organization, open communication, collaborative decision-making, and clear, measurable goals. By structuring teams around value streams, fostering regular communication between tech and business, involving stakeholders in key decisions, and setting data-driven objectives, startups can create an agile, cohesive environment where every tech initiative supports growth and enhances the company’s ability to meet its core objectives.</p><h3>Tools and Frameworks to Support Alignment</h3><p>Implementing the right tools and frameworks is essential for maintaining alignment between technology initiatives and business goals. These tools help startups set clear objectives, measure progress, and make data-informed decisions that drive meaningful outcomes. Here are two powerful frameworks that can support alignment within your team.</p><h4><strong>OKRs (Objectives and Key Results)</strong></h4><p>OKRs, or Objectives and Key Results, are a goal-setting framework that helps startups align tech projects with broader business objectives. This method involves defining clear, ambitious Objectives (what you aim to achieve) and Key Results (specific, measurable outcomes that indicate success) for each initiative. OKRs encourage teams to focus on impactful goals, measure progress effectively, and keep everyone aligned on the same mission.</p><ul><li><strong>How It Works</strong>: Startups set high-level Objectives that align with core business goals, such as “Improve user engagement” or “Increase product activation.” Each Objective is then paired with 3–5 measurable Key Results, such as “increase daily active users by 20% over the next quarter” or “achieve a 25% boost in user activation within three months.” By linking Key Results to concrete metrics, OKRs make it easy to track progress and assess the success of each initiative.</li><li><strong>Benefits of OKRs</strong>: OKRs provide a structured approach to goal-setting that promotes transparency and accountability. Teams understand how their work contributes to company-wide objectives, ensuring that each tech project is purposeful and directly supports business growth.</li><li><strong>Implementation</strong>: For each quarter or development cycle, hold a session to establish OKRs that align with your current strategic priorities. Revisit these OKRs regularly, using them to guide decision-making, prioritize resources, and adjust course when necessary.</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FL4N1q4RNi9I%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DL4N1q4RNi9I&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FL4N1q4RNi9I%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/3662bec2a041512eeb814dba62fbec32/href">https://medium.com/media/3662bec2a041512eeb814dba62fbec32/href</a></iframe><h4><strong>Data and Analytics Tools</strong></h4><p>Data and analytics are essential for understanding the real impact of tech initiatives on key business metrics. By using analytics tools, startups can track how their technology projects affect user engagement, acquisition, activation, retention, and more. This data-driven approach provides insights into what’s working and what needs improvement, helping teams stay agile and responsive to user needs.</p><p>By integrating these analytics tools, startups can continuously monitor the performance of tech initiatives and their impact on key business metrics. For instance:</p><ul><li><strong>User Engagement</strong>: Track daily active users, feature usage, and session duration to gauge how well a tech initiative enhances user engagement.</li><li><strong>Acquisition</strong>: Monitor the effectiveness of marketing-driven tech projects by analyzing traffic sources, sign-up rates, and conversion rates from acquisition channels.</li><li><strong>Activation</strong>: Use onboarding analytics to track activation rates, helping identify where users might struggle and optimize the onboarding experience for higher activation.</li><li><strong>Retention</strong>: Track retention metrics to understand if tech improvements lead to increased user loyalty, offering insights on features that enhance long-term user satisfaction.</li></ul><p>With access to real-time data, teams can quickly assess the impact of their initiatives and pivot when needed. For example, if data shows that users are dropping off during the onboarding process, the team can prioritize optimizations for that specific user journey to improve activation rates.</p><p>By leveraging frameworks like <strong>OKRs</strong> and <strong>data analytics tools</strong>, startups can maintain strong alignment between technology projects and business goals. OKRs ensure that each tech initiative directly supports strategic objectives, while analytics provide measurable insights into user behavior and project impact. Together, these tools create a structured, data-informed approach to building and iterating technology solutions that drive business growth and enhance the user experience.</p><h3>Conclusion and Next Steps</h3><p>Aligning technology strategy with business objectives is a powerful approach that enables startups to make strategic, high-impact tech investments that drive growth, enhance customer satisfaction, and support sustainable scalability.</p><p>By identifying core business goals, mapping tech initiatives to these objectives, prioritizing high-impact projects, building a culture of alignment, and utilizing effective tools and frameworks, startups can ensure that every tech decision contributes meaningfully to their overall mission.</p><h4><strong>Start Small, Think Big</strong></h4><p>For founders, the journey of tech alignment doesn’t have to be overwhelming. Begin by identifying one high-priority business goal, such as improving customer retention or boosting user acquisition, and focus on a tech initiative that directly supports this objective. As the results start to take shape, gradually expand to additional projects, iterating based on measurable outcomes and user feedback.</p><h4>Accelerate Your Path to Product-Market Fit!</h4><p><a href="https://www.raulgonzalez.tech/"><strong>Schedule a free consultation</strong></a> and discover how strategic tech alignment can drive rapid growth and maximize impact!</p><p><strong>Discover More Insights</strong>: Explore our blog for expert guides, success stories, and resources to help you align tech with growth. <a href="https://www.raulgonzalez.tech/"><strong>Visit our website now</strong></a> to dive deeper into strategies that drive results!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0904157370ff" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Real Impact of Culture, Leadership, and People on Startup Success]]></title>
            <link>https://medium.com/@Raulgzm/the-real-impact-of-culture-leadership-and-people-on-startup-success-d677a00930cf?source=rss-71d55c8ad440------2</link>
            <guid isPermaLink="false">https://medium.com/p/d677a00930cf</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Raúl González]]></dc:creator>
            <pubDate>Thu, 20 Jun 2024 10:14:32 GMT</pubDate>
            <atom:updated>2024-06-20T10:14:32.274Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>What truly drives the success of a startup?</blockquote><p>This burning question led James N. Baron and Michael T. Hannan, professors at Stanford University, to embark on a fifteen-year research journey. Studying over two hundred companies, they sought to uncover the key factors that influence a startup’s culture and overall success. Their findings were both surprising and illuminating.</p><blockquote>Culture Matters, Tremendously</blockquote><p>Baron and Hannan’s research revealed a fundamental truth: culture is critical. Through extensive interviews with CEOs, founders, leaders, and employees, they identified three main dimensions of organizational work and people management, each with distinct approaches.</p><ol><li><strong>Bonding and Care</strong>: This dimension explores how companies care for and engage their employees. They identified three types:</li></ol><ul><li><strong>Money</strong>: Prioritizing financial rewards.</li><li><strong>Work</strong>: Focusing on the nature and quality of the work itself.</li><li><strong>Love</strong>: Cultivating passion and emotional commitment.</li></ul><p><strong>2. Selection Criteria</strong>: This dimension examines how companies select new employees. The key factors here include:</p><ul><li><strong>Specific Skills</strong>: Hiring based on specialized skills.</li><li><strong>Exceptional Talent</strong>: Attracting outstanding talent.</li><li><strong>Cultural Fit</strong>: Ensuring alignment with the company’s culture.</li></ul><p><strong>3. Control and Coordination</strong>: This dimension looks at how work is managed and coordinated, revealing four types:</p><ul><li><strong>Direct Control</strong>: Managed directly by leaders.</li><li><strong>Professional Standards</strong>: Directed by top professionals and their standards.</li><li><strong>Formal Procedures</strong>: Based on established processes and formalities.</li><li><strong>Peer and Cultural Control</strong>: Managed by colleagues and the cultural norms of the organization.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*MxaxSSI_zmLZyoi8oUAIyg.png" /><figcaption>Dimensions of Employment Blueprints</figcaption></figure><p><strong>Blueprints for Organizational Success</strong></p><p>In their study “Organizational Blueprints for Success in High-Tech Start-Ups,” Baron and Hannan identified five distinct organizational categories, each representing a unique approach to structure and management within tech startups.</p><ol><li><strong>Engineering</strong>:</li></ol><ul><li><strong>Description</strong>: Focused on technical excellence and innovative product development.</li><li><strong>Characteristics</strong>: Engineer-driven culture, autonomy, technical creativity, decentralized decision-making, technical competence over hierarchy.</li></ul><p><strong>2. Star</strong>:</p><ul><li><strong>Description</strong>: Aims to attract and retain top-tier talent.</li><li><strong>Characteristics</strong>: High incentives, recognition, professional development opportunities, competitive and meritocratic culture, reliance on individual performance.</li></ul><p><strong>3. Bureaucracy</strong>:</p><ul><li><strong>Description</strong>: Relies on formal processes and clear hierarchical structures to manage growth and complexity.</li><li><strong>Characteristics</strong>: Implementation of rules and procedures, centralized decision-making, focus on operational efficiency and predictability, clear communication and responsibilities.</li></ul><p><strong>4. Autocracy</strong>:</p><ul><li><strong>Description</strong>: Control and direction are concentrated in the hands of a few leaders, often the CEO.</li><li><strong>Characteristics</strong>: Rigid hierarchical structures, highly centralized decision-making, top-down communication, strict adherence to leader directives.</li></ul><p><strong>5. Commitment</strong>:</p><ul><li><strong>Description</strong>: Focused on building a strong, cohesive culture based on mutual commitment and shared values.</li><li><strong>Characteristics</strong>: Family-like atmosphere, trust, deep commitment to the company’s mission and values, participative decision-making, emphasis on job stability and long-term development.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8_1z5MW30WKcrsshD1xT1A.png" /><figcaption>Typology of Employment Blueprints, Based on Three Dimensions</figcaption></figure><p><strong>Which Model Works Best?</strong></p><p>Unsurprisingly, bureaucracies and autocracies generally performed the worst in terms of company success. The Engineering model had mixed results, excelling in some industries while failing in others. The Star model produced remarkable success stories but also came with high risks due to the management challenges posed by high egos and strong personalities.</p><p>The standout model, however, was Commitment. Remarkably, no company with a Commitment-based culture failed. Not only were these companies more profitable, but they were also more attractive to investors. The Commitment model fostered a cohesive, trust-based environment that drove long-term success and innovation.</p><p><strong>Conclusion</strong></p><p>James N. Baron and Michael T. Hannan’s study reveals that while there is no single magic formula for startup success, the Commitment model stands out as particularly effective. By building a strong, cohesive culture rooted in mutual commitment and shared values, startups can achieve high performance, innovation, stability, and employee satisfaction. This insight highlights the importance of fostering an environment of trust and collaboration, which can be decisive for the long-term success and sustainability of tech startups. Entrepreneurs can use these findings to design organizations that not only innovate and grow but also remain resilient and sustainable over time.</p><p><a href="https://static1.squarespace.com/static/58d057ba2994ca536bbf98dd/t/5cb4d8aa15fcc049b83e82d9/1555355820139/Organizational+Blueprints+for+Success+-+Standford+Project.pdf">https://static1.squarespace.com/static/58d057ba2994ca536bbf98dd/t/5cb4d8aa15fcc049b83e82d9/1555355820139/Organizational+Blueprints+for+Success+-+Standford+Project.pdf</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d677a00930cf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Desvelando el papel de la cultura en startups exitosas: Estudio de Baron y Hannan]]></title>
            <link>https://medium.com/@Raulgzm/desvelando-el-papel-de-la-cultura-en-startups-exitosas-estudio-de-baron-y-hannan-246d3ce8ef72?source=rss-71d55c8ad440------2</link>
            <guid isPermaLink="false">https://medium.com/p/246d3ce8ef72</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Raúl González]]></dc:creator>
            <pubDate>Thu, 20 Jun 2024 10:08:54 GMT</pubDate>
            <atom:updated>2024-06-20T10:08:54.110Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>¿Cuál es el impacto real de la cultura, del tipo de liderazgo y las personas en el éxito de una “<em>Startup</em>”?</blockquote><p>Esta es la pregunta que James N. Baron y Michael T. Hannan, profesores en la Universidad de Stanford, se plantearon y decidieron realizar una investigación basada en evidencia para encontrar una respuesta.</p><p>Durante quince años y más de doscientas empresas, investigaron cada factor con impacto en la cultura de una empresa, con el fin de encontrar esas evidencias y dicha respuesta. Lo que encontraron los dejó marcados.</p><p>El primer descubrimiento fue simple y directo: la cultura importa, y mucho.</p><blockquote>La cultura importa, y mucho.</blockquote><p>Después de estudiar a estas doscientas empresas y entrevistar a CEOs, fundadores, líderes y empleados, descubrieron que los enfoques sobre cómo debería ser la organización del trabajo y las personas variaban en tres dimensiones principales, cada una con tres o cuatro enfoques distintos.</p><ol><li><strong>Vinculación / Cuidado</strong>: Se descubrieron tres diferentes tipos de vinculación y cuidado del empleado, las cuales se etiquetaron como: <strong>dinero</strong> (money), <strong>tipo de trabajo</strong> (work), y <strong>pasión</strong> (love).</li><li><strong>Criterios para la selección</strong>: esta dimensión analiza cómo se realizaba la selección de las personas que se unían a la empresa. Acorde con este criterio se encontraron los siguientes factores: selección por <strong>skills</strong> específicos, escoger por <strong>talentos excepcionales</strong> y, finalmente, optar por seleccionar dependiendo del <strong>encaje cultural</strong> con el equipo.</li><li><strong>Control / Coordinación</strong>: la tercera dimensión estudia cómo se realiza la coordinación y el control sobre el trabajo de esas personas. Se hallaron cuatro tipos distintos: un <strong>control directo</strong> desde los propios líderes, un <strong>control profesional</strong> dirigido desde los mejores profesionales contratados y en sus estándares, un control más tradicional basado en <strong>procedimientos y procesos formales</strong>, y un último grupo donde eran los propios compañeros de trabajo cercanos y la <strong>organización cultural</strong> los que realizaban ese control.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*MxaxSSI_zmLZyoi8oUAIyg.png" /><figcaption>Dimensions of Employment Blueprints</figcaption></figure><p>En su estudio “Organizational Blueprints for Success in High-Tech Start-Ups,” James N. Baron y Michael T. Hannan identificaron cinco categorías distintas de organizaciones. Cada una de estas categorías representa un enfoque único hacia la estructura organizativa y la gestión dentro de las startups tecnológicas.</p><ol><li><strong>Ingeniería (Engineering)</strong>:</li></ol><ul><li><strong>Descripción</strong>: Este tipo de organización se centra en la excelencia técnica y el desarrollo de productos innovadores. La prioridad es la calidad técnica y la resolución de problemas complejos.</li><li><strong>Características</strong>: Predomina una cultura de ingenieros, con un enfoque en la autonomía y la creatividad técnica. Las decisiones se toman de manera descentralizada y se valora la competencia técnica sobre la jerarquía formal.</li></ul><p>2. <strong>Estrella (Star)</strong>:</p><ul><li><strong>Descripción</strong>: Aquí, el enfoque principal es atraer y retener a talentos excepcionales, considerados como estrellas en su campo.</li><li><strong>Características</strong>: Las organizaciones estrella suelen ofrecer incentivos elevados, reconocimiento y oportunidades de desarrollo profesional para sus empleados más talentosos. La cultura es altamente competitiva y meritocrática, con una fuerte dependencia en el desempeño individual.</li></ul><p>3. <strong>Burocracia (Bureaucracy)</strong>:</p><ul><li><strong>Descripción</strong>: Este tipo de organización se basa en la formalización de procesos y estructuras jerárquicas claras para gestionar el crecimiento y la complejidad.</li><li><strong>Características</strong>: Predomina la implementación de reglas y procedimientos formales. La toma de decisiones es centralizada y se enfoca en la eficiencia operativa y la previsibilidad. La comunicación y las responsabilidades están claramente definidas.</li></ul><p>4. <strong>Autocracia (Autocracy)</strong>:</p><ul><li><strong>Descripción</strong>: En las organizaciones autocráticas, el control y la dirección están concentrados en manos de unos pocos líderes o fundadores. A menudo el propio CEO.</li><li><strong>Características</strong>: Estas organizaciones tienen estructuras jerárquicas rígidas, donde la toma de decisiones es altamente centralizada. La comunicación es de arriba hacia abajo y se espera que los empleados sigan las directrices establecidas por los líderes sin cuestionarlas.</li></ul><p>5. <strong>Compromiso (Commitment)</strong>:</p><ul><li><strong>Descripción</strong>: Estas organizaciones se centran en construir una cultura sólida y cohesiva, basada en el compromiso mutuo y los valores compartidos.</li><li><strong>Características</strong>: Fomenta una atmósfera familiar y de confianza, donde se espera que los empleados estén profundamente comprometidos con la misión y los valores de la empresa. Las decisiones a menudo se toman de manera participativa y se enfatiza la estabilidad laboral y el desarrollo a largo plazo.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8_1z5MW30WKcrsshD1xT1A.png" /><figcaption>Typology of Employment Blueprints, Based on Three Dimensions</figcaption></figure><h3>¿Cuál de estos modelos funcionó como el mejor?</h3><p>Sin que le pueda sorprender a nadie las <strong>burocracias y autocracias</strong> tendieron a ser las que funcionaron con peor rendimiento en términos de éxito de las compañías.</p><p>Mientras, el modelo “<strong>Engineering</strong>” tuvo sus aciertos y errores. En ciertas industrias funcionó relativamente bien, mientras que en otras fue todo lo contrario.</p><p>Después está el modelo “<strong>Star</strong>”. Este enfoque produjó algunas compañías exitosas donde poner a personas con un talento increible en un mismo equipo produjo resultados increibles. Sin embargo, este enfoque se ha desmostrado que viene con un alto riesgo. Las compañías en esta categoría o tuvieron éxito o desaparecieron. Por qué? el principal motivo vino de la alta carga de gestión de los altos egos y personalidades dentro del equipo, lo que terminó siendo una gran barrera en el éxito a largo plazo.</p><p>La manera más efectiva, y que quedó reflejada en el estudio, de obtener resultados fue a través del modelo de “<strong>Commitment</strong>”. Ninguna de las firmas estudiadas, y que su cultura recaia dentro de esta categoría, fallaron. Ninguna de ellas. No solo eso, si no que todas estas compañías fueron más rentables y más atractivas para inversores.</p><p>En conclusión, el estudio de James N. Baron y Michael T. Hannan revela que no existe una única fórmula mágica para el éxito en las startups tecnológicas, pero destaca que el modelo de Compromiso (Commitment) sobresale por encima del resto. Este enfoque, basado en la construcción de una cultura sólida y cohesiva, donde los valores compartidos y el compromiso mutuo son primordiales, demostró ser especialmente efectivo. Las organizaciones que adoptaron el modelo de Compromiso no solo lograron un alto rendimiento y una innovación constante, sino que también mostraron una mayor estabilidad y satisfacción entre los empleados. Este hallazgo subraya la importancia de fomentar un ambiente de confianza y colaboración, lo cual puede ser decisivo para el éxito y la sostenibilidad a largo plazo de las startups tecnológicas. Al aplicar estos insights, los fundadores y líderes pueden diseñar organizaciones que no solo innoven y crezcan, sino que también sean resilientes y sostenibles en el tiempo.</p><p>El estudio de Baron y Hannan proporciona un marco valioso para que los emprendedores entiendan cómo las diferentes estructuras organizativas pueden afectar el desempeño y la cultura de sus empresas.</p><p><a href="https://static1.squarespace.com/static/58d057ba2994ca536bbf98dd/t/5cb4d8aa15fcc049b83e82d9/1555355820139/Organizational+Blueprints+for+Success+-+Standford+Project.pdf">https://static1.squarespace.com/static/58d057ba2994ca536bbf98dd/t/5cb4d8aa15fcc049b83e82d9/1555355820139/Organizational+Blueprints+for+Success+-+Standford+Project.pdf</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=246d3ce8ef72" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to get started working on small things — Breaking down user stories]]></title>
            <link>https://medium.com/@Raulgzm/how-to-get-started-working-on-small-things-breaking-down-user-stories-3326546ed741?source=rss-71d55c8ad440------2</link>
            <guid isPermaLink="false">https://medium.com/p/3326546ed741</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[user-stories]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Raúl González]]></dc:creator>
            <pubDate>Fri, 15 Sep 2023 08:00:44 GMT</pubDate>
            <atom:updated>2023-09-16T09:38:41.017Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to get started working on small things — Breaking down user stories</h3><p><em>Learning how to split user stories can be a game-changer. Break down user stories into smaller tasks to tackle big projects more efficiently. Start today and increase your focus and productivity.</em></p><p>Picture this: you have assembled your product layer by layer, like a carefully crafted cake. First comes the base, then the mousse, followed by another layer, then the fruit layer, then the cream, and finally, the decorations. But after all that effort, when your users take a bite, guess what? They don’t like it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*qIfv8t2hc4yUG8USOR7exA.png" /></figure><p>If we want to go faster, it’s essential to capture, write, and split user stories effectively. We’ve previously discussed what a user story is: <a href="https://medium.com/@Raulgzm/are-you-sure-you-know-what-a-user-story-is-what-stories-really-are-bc4877a9456a">https://medium.com/@Raulgzm/are-you-sure-you-know-what-a-user-story-is-what-stories-really-are-bc4877a9456a</a>.</p><p>Here, we are going to see that the goal of a user story is to describe and create increments of user value that can be implemented by a development team in a short amount of time, typically on the order of hours or, at most, a few days (1–2)</p><p>The beauty of creating individual small stories is that they can stand alone and still make a more significant impact when compiled into a larger feature. Remember to gather feedback and make necessary adjustments along the way, always.</p><p>Creating good user stories will have a tremendous impact on predictability within our teams, which will be discussed in a future post.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/572/0*tRS_fK1GxxKpueQv.png" /></figure><h3>Does this deliver value to the user?</h3><p>Many teams struggle to split large user stories and features into good, small stories. Fortunately, story splitting is a skill that can be learned in a relatively short time.</p><p>Years ago, INVEST was coined by Bill Wake, Extreme Programming pioneer, to describe the six essential characteristics of a good user story.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*A21_4yNLB3evt31m.png" /></figure><ul><li><strong>Independent</strong>: Every single story has the potential to be released.</li><li><strong>Negotiable</strong>: The development team can negotiate the story’s scope and contents with the product owner, encouraging all team members to contribute good ideas.</li><li><strong>Valuable</strong>: Each story has its own value for the user.</li><li><strong>Estimable</strong>: Each story is concrete enough that the delivery team can give an approximate estimate as to how big the story is if needed.</li><li><strong>Small</strong>: The team can receive quick feedback by completing the story in a short amount of time.</li><li><strong>Testable</strong>: The story can be tested. In the agile world, “tested” means that a set of automated tests, including unit, integration, and acceptance tests, is delivered with the production code.</li></ul><h3>Story-splitting techniques</h3><p>There are many techniques for splitting stories. Here are some of the more useful ones:</p><h4>Split by capabilities offered</h4><p>One of the most apparent methods to divide a substantial feature is to examine the various functionalities it offers and separate each one into individual stories. For instance, the abilities to <strong>search</strong>, <strong>filter</strong>, and <strong>sort</strong> can be split into separate stories. Additionally, each method of searching or sorting can be further separated into its own story.</p><h4>Split user stories by workflows</h4><p>First, define the workflows and actors for your product. For instance, cooks upload images, while users view them and have cooking notebooks.</p><p><strong>Big User Story<br></strong><em>As a Rider, I want to manage my account<br></em><strong>Split User Story<br></strong><em>As a Rider, I want to upgrade my account<br>As a Rider, I want to change my profile picture<br>As a Rider, I want to change my address</em></p><h4>Split by User Roles or User Personas</h4><p>System administrators and teachers have unique roles and needs when interacting with software. Splitting features and stories based on these roles results in better user experiences.</p><p>Users interact with software differently, even if they have the same role. Power users prefer keyboard shortcuts while casual users prefer intuitive assistance. Handicapped users may require alternative methods of interaction to complete the same tasks as other users.</p><h4>Split by target device</h4><p>When designing your system, it’s important to consider that users may not interact with it using a standard computer. This means you need to take into account various smartphones and IoT devices. To provide a more natural experience for your users, it’s best to split stories by device. You can group them by platform, which includes operating systems (such as Mac and Windows), device types (like phones, tablets, and desktops), browsers (including Internet Explorer, Chrome, and Opera), or anything else that applies to your project.</p><p><strong>Big User Story</strong>:<br><em>As a cook, I want to upload images of my recipe so that my starving fans can have a real picture of how the recipe looks like<br></em><strong>Split User Story:<br></strong><em>As a cook, I want to upload images of my recipe using a laptop<br>As a cook, I want to upload pictures of my recipe from my phone<br>As a cook, I want to upload photos of my recipe using IE<br>As a cook, I want to upload pictures of my recipe using Chrome</em></p><h4>Split user stories by data types.</h4><p>Your product is designed to display currency and units of measure based on the user’s location. This means that users in the US will see USD and pints while users in France will see EUR and litres for the same recipes. This makes the application truly international while still catering to individual user preferences.</p><p><strong>Big User Story:<br></strong><em>As an eater, I want to load the ingredients of my recipes with the right qualities<br></em><strong>Split User Stories:<br></strong><em>As an eater, I want to see the quantities of the ingredients in the metric system<br>As an eater, I want to see the amounts of the ingredients in the English system</em></p><h4>Split user stories in Agile by Cutting the user stories by complexity</h4><p>A clear way to apply this approach is to contrast manual and automated functionality.</p><p><strong>Big User Story</strong>:<br><em>As a user, I want to subscribe automatically <br></em><strong>Split User Story:<br></strong><em>As a user, I want to subscribe manually<br>As a user, I want to receive an email with all the information about my subscription</em></p><h4>Split user stories by CRUD type of operations</h4><p>CRUD stands for:<br>C = create<br>R = read<br>U = update<br>D = delete<br>They are standard operations the users can do.</p><p><strong>Big user story:<br></strong><em>As a cook, I want to manage my recipes for the benefit of sharing them with the entire world<br></em><strong>Split User Story:<br></strong><em>As a cook, I want to create a recipe<br>As a cook, I want to read the recipe that I just created a recipe<br>As a cook, I want to update my recipes<br>As a cook, I want to delete my recipes</em></p><h4>Split using zero/one/many method</h4><p>After utilizing various of these previous techniques to distinguish valuable stories and dividing them into smaller pieces, you may still have stories that are too extensive. In such cases, implementing the “zero/one/many” rule can be beneficial for the team to stimulate creativity and keep breaking down stories into manageable vertical slices.</p><p>With the zero/one/many approach, you ask these three questions:</p><ul><li>What happens if we are dealing with nothing?</li><li>What happens if we are dealing with one thing?</li><li>What happens if we are dealing with many things?</li></ul><p><strong>Big user story:</strong><br><em>As a teenager, I want to borrow books so that I can enjoy reading that would otherwise be unavailable to me.</em><br><strong>Split User Story:</strong><br><em>As a user, I want to know that the library is empty so that I don’t waste my time trying to borrow books that are not available.<br>As a user, I want to be able to read a book in the digital library so that I can enjoy it.<br>As a user, I want to borrow from a bounty of books so that I can enjoy reading that would otherwise be unavailable to me.</em></p><p>Other ways to apply Zero/One/Many:</p><ul><li>Messaging: No messages / First Message / Many Messages</li><li>Shopping Cart: Empty Car / One Thing / Many Things</li><li>Games: Single-player / Multi-Player</li></ul><figure><img alt="How to Write Great User Stories. Wherever I go or whoever I speak about… |  by Serkan | Medium" src="https://cdn-images-1.medium.com/proxy/1*Ro9ocQLorpXTu1Rvki8rqQ.gif" /></figure><p>We’d love to help you get better at story splitting and other key Product Engineering skills. Contact me about private training and coaching for your organization: <a href="https://www.raulgonzalez.tech/">https://www.raulgonzalez.tech/</a></p><h4>Other Interesting Resources:</h4><ul><li>The best source for that is @jeffpatton’s book <a href="https://www.amazon.com/User-Story-Mapping-Discover-Product/dp/1491904909">“User Story Mapping.”</a> There are a bunch of pictures.</li><li>Extreme programming User Stories: <a href="http://www.extremeprogramming.org/rules/userstories.html">http://www.extremeprogramming.org/rules/userstories.html</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3326546ed741" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Are You Sure You Know What a User story Is? what stories really are.]]></title>
            <link>https://medium.com/@Raulgzm/are-you-sure-you-know-what-a-user-story-is-what-stories-really-are-bc4877a9456a?source=rss-71d55c8ad440------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc4877a9456a</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[user-stories]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[extreme-programming]]></category>
            <dc:creator><![CDATA[Raúl González]]></dc:creator>
            <pubDate>Fri, 08 Sep 2023 11:39:40 GMT</pubDate>
            <atom:updated>2023-09-16T09:39:08.656Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>A user story is not simply a task that follows the “As a… I need…” format, nor is it a Jira/Shortcut/ClickUp or whatever ticket.</em></blockquote><p>The concept of a user story has been frequently misinterpreted, both historically and at present.</p><p>I believe that one issue with user stories stems from the misconception that Agile teams must present their work in story format, leading some teams to force their work into a narrative structure instead of focusing on the user’s needs. This can occur when teams attempt to transition from a traditional waterfall approach to the Agile mindset.</p><p>It is essential that user stories prioritize delivering value for the user, rather than merely accomplishing technical tasks. Technical tasks are not the source of user stories. It must be kept in mind that not all work warrants inclusion in a user story. Your assigned duties are distinct from the user story, as it is solely your responsibility to carry out the task, not the user’s.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*whhRI7syBL09jMFE.jpg" /></figure><p>The point of a user story is NOT to define your work. A backlog is NOT a list of things to do. A user story describes your users/customers working on things that are valuable to them. The whole point is to identify ways to make our customer’s lives better. Those are the things that are worth expending effort on. We decide what to do by identifying what our user/customer needs us to do to make their lives better. If you turn your backlog into a to-do list of technical tasks, you lose all of that.</p><p>In the realm of work, there exist two types: value-adding work that is appreciated by the user, and other work that you personally think holds value. The secret lies in striking a balance between the two. If you devote too much time to the latter, the risk of losing your clientele increases, potentially causing your business to flounder. Consequently, it is vital to make wise decisions regarding the work you undertake.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/848/0*PgKy9cgtOLk47SG3.jpg" /></figure><blockquote>“technical user story” doesn’t actually exist</blockquote><p>It’s important to note that a “technical user story” doesn’t actually exist. A user story should be based on what your user communicates to you. It should depict your user’s work, not yours. The term “story” shouldn’t be interpreted as referring to “any random programmer task”. Technical aspects are merely implementation details that support a story, rather than being a story in themselves.</p><p>A technical user story is overhead. Calling it “overhead” emphasizes its revenue-negative impact and provides the proper perspective. User stories should describe a specific task that a person in a certain role completes to achieve a beneficial outcome within a domain in your business.</p><p>For example, Login is not a user story. Period. No user has ever logged in, thought they’d accomplished something valuable just by logging in, then logged out.</p><p>Let’s see a small trick when you hear something similar to “I need to create a report”. The first question to ask is:</p><blockquote><em>“What exactly are your users going to do with the “data” in that report?”</em></blockquote><p>Simply presenting raw data is rarely useful. If your users use your report to do something, that “something” is your story, not the report generation.</p><blockquote><em>“</em>As a manager, I can print a pie chart showing tickets broken down by engineer, so that I can quickly tell if any engineers are overloaded”</blockquote><p>That’s not really a user story as it focuses on a solution rather than a problem. If the issue is determining whether the engineers are overburdened, a pie chart of tickets may not suffice. User stories should address problems, and the process involves iterative exploration toward an ideal solution.</p><p>One way to try to avoid this problem is to shuffle around the extra-format thinking: In order to provide &lt;this outcome that’s valuable in the domain&gt;, &lt;someone in role X&gt; does &lt;this work in the domain&gt;.</p><blockquote><em>“As a checking account holder, I want to deposit a check from my mobile device, so that I don’t have to waste time going to the bank”</em></blockquote><blockquote><em>“As a checking account holder, I want to save my credentials, so that I don’t have to input my username and password each time I log in”</em></blockquote><blockquote><em>“As a user, I want to invite my friends, so we can enjoy this service together”</em></blockquote><blockquote><em>“As a manager, I want to be able to understand my colleagues’ progress, so I can better report our successes and failures”</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*bKieXRuZqdDODJJM.gif" /></figure><p>Another interesting point worth mentioning is:</p><h4><strong><em>- You are not the user.</em></strong></h4><h4><strong><em>- The PO/PM is not the user.</em></strong></h4><h4><strong><em>- The CEO is certainly not the user.</em></strong></h4><p>The user is the user. A user story is the user’s story. A user story is just that — a story of the user at work.</p><blockquote><em>The human species thinks in metaphors and learns through stories. </em>Mary Catherine Bateson</blockquote><p>If you are interested, I offer workshops for both product managers and developers. In these workshops, you will learn how to capture, refine, split, and manage user stories, as well as how to collaborate to turn those stories into working code:</p><p><a href="https://www.raulgonzalez.tech/">Raúl González - We help your company go faster</a></p><p>Other Interesting Resources:</p><ul><li>The best source for that is @jeffpatton’s book <a href="https://www.amazon.com/User-Story-Mapping-Discover-Product/dp/1491904909">“User Story Mapping.”</a> There are a bunch of pictures.</li><li>Extreme programming User Stories: <a href="http://www.extremeprogramming.org/rules/userstories.html">http://www.extremeprogramming.org/rules/userstories.html</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc4877a9456a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Looking for major success? Sleep better.]]></title>
            <link>https://medium.com/@Raulgzm/looking-for-major-success-sleep-better-fb38d4d31160?source=rss-71d55c8ad440------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb38d4d31160</guid>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[performance-management]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Raúl González]]></dc:creator>
            <pubDate>Mon, 29 Nov 2021 17:37:34 GMT</pubDate>
            <atom:updated>2023-09-16T09:39:20.241Z</atom:updated>
            <content:encoded><![CDATA[<p>Achieving optimal sports performance is a major goal for everyone involved in any type of physical activity, whether professional or amateur. Could we apply all the knowledge about sports performance to our work and thus achieve greater success in our professional careers?</p><p>Does this question make sense? That is the purpose of this article.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wEFHCKe13HQBPE3X0PX0OQ.jpeg" /></figure><p>Sports performance is built over three fundamental pillars: training, nutrition, and rest. The right balance between these three pillars will help the body to progress and reach the sporting goals set.</p><p>This balance is a fundamental requirement to preserve the health of the different systems of our organism in order to optimize sports performance. Ensuring an adequate food intake according to the training load, as well as respecting recovery periods, and getting enough sleep, are necessary conditions to optimize sports performance.</p><p>These three pillars directly impact the four factors that determine the performance: physical, technical, tactical, and psychological.</p><p>So, could we establish the feasibility of comparing our work with a sports discipline?</p><p>As we have seen before, the first pillar is training. However, we can understand practice in two different ways: mental or physical exercise.</p><p>If we understand training as a mental exercise, it seems evident that the activity affects technical, tactic, and psychological factors. Training can improve any discipline to the point of mastery.</p><p>Now, we can consider whether investing time in improving our physical condition through exercise has a direct impact on the way we work on a daily basis. Our physical condition will determine our energy, our ability to concentrate, how well we perform in our daily work routine. Additionally, training coupled with good nutrition habits and adequate sleep will improve our immune system. In this way, we will have fewer “injuries” in our working “season”; therefore, we will obtain more performance.</p><p>Science has proven all this through several studies. Nevertheless, it is also true that the Greeks already knew that constant exercise is a shield that protects our brain, stimulates learning and memory. Exercise produces a molecule called “Brain-derived neurotrophic factor” (BDNF), fundamentally related to the capacity for growth and plasticity of neuronal connections, and learning is nothing more than brain changes in synaptic levels. Therefore, we can conclude that physical health leads to better mental health.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SnZF-40SuoEhrpqEP-sw8g.jpeg" /></figure><p>That being said, training is not the only thing that affects our brain, but also what we eat. Some foods are vital for our brain, such as Omega-3 fatty acids. Without this Omega-3, we would have to stop doing many things because it is a brick for our brain. The answer to this question is in the water because life comes from the sea, which explains why these fatty acids are mainly in fish.</p><p>Another example of vital food for our brain is folic acid. Also known as Vitamin B9, this vitamin is essential for cellular detoxification, neurotransmitter production, and slowing down cognitive decline. Folic acid can enable us to increase our mental health in the elderly.</p><p>However, the excellent effects of nutrition are silent results, and we must turn them into habits to experience their outcomes. Not perceiving immediate results does not mean this is not important or necessary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EeIWH0y3A8O0CHOrI7wE8w.jpeg" /></figure><p>This leads me to the final point, which is sleep and rest. Do you think those aspects affect our brain and body? Do you remember a time when you were unable to sleep well and how you felt the next morning? According to the latest researches, sleeping less than eight hours a night is linked to cognitive decline and memory loss. That is, this sleep deprivation has an effect on the mental capacity to learn, think, argue, problems solving, make decisions, memory, and attention capacity. We can not build nor maintain the brain’s pathways that allow us to learn without sleep.</p><p>While we sleep, our brain is occupied removing toxins, restoring wear and tear caused by daily use, labeling, and generating memories. The brain is constantly collecting information while we sleep, even if not consciously. It is thanks to its great plasticity, which allows us to store throughout the day data that is processed while we sleep. And although science does not know the reasons yet, some research has confirmed that our brain actives areas related to creativity and learning while we sleep.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zyFrupGFhMDhH-fa1DHVMw.jpeg" /></figure><p>With this in mind, we can conclude that the three fundamental pillars of performance can be applied not only to sports but also to the mental sphere, state of mind, and physical condition. It may seem obvious, but for some reason, we find it hard to realize that it is actually a spiral. If you don’t exercise, your mental and physical states will be worse. In those states, it will be harder to exercise every day. Working long hours will not let you exercise, eat healthily or get adequate sleep. Inevitably this will lead you to a worse physical and mental state, which will lead you to work longer hours to counteract that low performance.</p><blockquote>Working long hours will not let you exercise, eat healthily or get adequate sleep. Inevitably this will lead you to a worse physical and mental state, which will lead you to work longer hours to counteract that low performance.</blockquote><p>Finally, it may be concluded that everything we know about sports performance should apply to our professional career. Investing time in these three fundamental pillars of sports performance would augur us more effectiveness and bigger professional results.</p><blockquote><strong>In essence, if you abandon your body, your brain will follow.</strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb38d4d31160" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You will play in the same way you train]]></title>
            <link>https://medium.com/@Raulgzm/you-will-play-in-the-same-way-you-train-521d8babe6ff?source=rss-71d55c8ad440------2</link>
            <guid isPermaLink="false">https://medium.com/p/521d8babe6ff</guid>
            <category><![CDATA[quality]]></category>
            <category><![CDATA[quality-software]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[mindset-coaching]]></category>
            <category><![CDATA[quality-management]]></category>
            <dc:creator><![CDATA[Raúl González]]></dc:creator>
            <pubDate>Sun, 21 Nov 2021 16:03:33 GMT</pubDate>
            <atom:updated>2021-11-21T16:14:50.732Z</atom:updated>
            <content:encoded><![CDATA[<p>I have played football since I was a kid. Football taught me a lot of things beyond controlling the ball or hitting it. I learned values that the sport teaches thanks to the labor coaches perform, but also, thanks to things that a team teaches. The first thing that each coach takes care of teaching you is something you always will remember: “You will play in the same way you train”. It is a quote that hides numerous things that can not be seen to the casual eye.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SKCxX72le_SMG3gVZrIDog.jpeg" /></figure><p>At first sight, we can simply read that If you train badly, you play badly, and If you work harder and pay attention to details in training, you will play in the same way. However, the quote contains many others purposes. That quote hides that the meaning of “play better” is the search for quality and excellence in something. It desires to transmit that quality is not a mere consequence of following a set of behaviors in a particular moment. Quality should be a prerequisite, something that is pretended previously as a self demand.</p><p>Quality is, of course, a philosophy, a way of thinking where you can not just say it is important. It is inevitable to believe in; it is a way of life, even it is necessary to breathe it. In any other way, it would be very difficult to force us into each process to pursue every detail mentally.</p><p>I would like to specify that this way of thinking and act is not against work methodologies like “Lean” because as wrong is to do things prematurely as after the deadline. It is not against that accept the error either, quite the opposite, errors are essential parts of this process, in the creativity, innovations and other changes. Likewise, I don’t want to say that quality must be your primary value or indispensable to be successful. However, you, my dear reader, will agree that you have more probability of winning matches playing well than playing badly.</p><p>Nowadays, it seems to start to establish a micro-culture where a person who pretends a well-done work, a work of quality, or where there are no small and unimportant details, could be controversial or even problematic. We should not permit that this could progress. We should remember those learnings and convert them into a recipe, a method we can export to many other fields in life like education, business, ONGs, public administrations, politics, etc. It can be we have forgotten those lessons. However, we learned when we were kids that, in sports and life, without those lessons wouldn’t reach big things.</p><p>I should add that if to be a person who pushes herself, who wants to outdo herself, and who loves what she does is to be someone obsessive; If to be a person who wants to be professional, who pretends and demand quality is to be someone problematic; Then I want obsessive and problematics persons in my teams. I use to use a metaphor to explain this. In music, you won’t find this micro-culture. There is no space for that. A musician never wants to go out of tune. A musician looks for a particular and exact sound, a sound of quality with which she can delight her audience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*FGRyuHQJz2PJyPi6ygpbog.jpeg" /></figure><p>If you aspire to a work of quality, you need to prove it day by day, detail by detail. You need to have self-discipline and a love for well-done jobs. You will play in the same way you train because, as you already know, the small details make big differences.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=521d8babe6ff" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Would you wear a t-shirt with your company logo on it?]]></title>
            <link>https://medium.com/@Raulgzm/would-you-wear-a-t-shirt-with-your-company-logo-on-it-217856daa0db?source=rss-71d55c8ad440------2</link>
            <guid isPermaLink="false">https://medium.com/p/217856daa0db</guid>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Raúl González]]></dc:creator>
            <pubDate>Wed, 15 Nov 2017 08:45:18 GMT</pubDate>
            <atom:updated>2017-11-15T08:59:31.053Z</atom:updated>
            <content:encoded><![CDATA[<p>The answer for this question was necessary because people relate to what you believe in, not what you do. If we can build a stronger bond with a person, it is much easier to work with them.</p><p>At Brainattica, we sometimes met to talk about company culture. We shared the things we did and inspired each other to try out new practices in order to continuously improve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*tpK2Q1fZeBriLfp2CrKR9Q.jpeg" /></figure><p>A team has only really achieved an identity when people are eager to wear the symbols of that team. But how do we achieve this? How do we create a company to which people want to belong? How do we achieve that you want wear a t-shirt with our logo?</p><p>We need a new perspective built much more around intrinsic motivation. Around the desire to do things because they matters, because we like it, they’re interesting or part of something important.</p><p>We are going to think in three elements:</p><ol><li><strong>Autonomy</strong>. Autonomy as the urge to direct our own lives.</li><li><strong>Mastery</strong>. Mastery as the desire to get better and better at something that matters</li><li><strong>Common Purpose</strong>. And Common Purpose as the wish to do what we do in the service of something larger than ourselves.</li></ol><p>When many of us think about innovation, we think about an “Aha!” moment. But we all know that’s a myth. Innovation is not about solo genius, it’s about collective genius.</p><p>Innovation it’s a type of collaborative problem solving, usually among people who have different expertise and different points of view.</p><p>In innovative environments the differences are amplified, don’t minimize them. Innovative companies don’t have brainstorming, where people suspend their judgment. They know to have very heated but constructive arguments to create a portfolio of alternatives.</p><p>Individuals in innovative organizations learn how to inquire, they learn how to actively listen, but guess what? They also learn how to advocate for their point of view. They understand that innovation rarely happens unless you have both diversity and conflict.</p><p>If we want to build a company that can innovative time and again, we must lead the way. Leading innovation is about create the space where people are willing and able to do the hard work of innovative problem solving.</p><p>The leaders focus on building a sense of community. Talented people don’t want to follow us anywhere, they want to co-create with us the future.</p><p>How do we define leadership? Leadership es about creating a company to which people want to belong.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*9KFY7kunohdNcGTiysyTCw.jpeg" /></figure><p>How do we see our role? we’re a human glue, we’re a connector and we’re an aggregator of viewpoints, we’re never a dictator of viewpoints. We’re the social architects. We’re creating the space where people are willing and able to share and combine their talents and passions.</p><p>Very few managers are leaders. The difference between the two? A manager is someone who has people reporting to him. A leader is someone who people will follow, even if they don’t report to him.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*0USYtULCB_-as_DQBgrWNA.png" /></figure><p>When the leader establishes trust within the team, it truly shows. Team members feel secure in sharing their opinions without the fear of judgment or retribution, freely share information and openly collaborate on projects and know that if the leader pushes them, he does so with their best interests in mind. The result? Highly motivated and productive workforce.</p><p>A leader is only as effective as his team. But building trust takes time and conscious effort. People don’t trust words, they trust actions. Trust leads to loyalty. And loyalty leads to people doing their best to deliver results for you and the company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*sNKPHAKQNve_JWmcID2aTA.jpeg" /></figure><p>Wow! This is what we say when We’re seeing our colleagues being proud of our brand. It makes us even more proud to be working at our company!</p><p>…and you, would you wear a t-shirt with the logo of your company on it?</p><p>“Scorpions are very loyal to their cyclone. If one of them is attacked, all the others dive in. And we, all of us, we’re a cyclone”.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=217856daa0db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Securing Golang API using Json Web Token (JWT)]]></title>
            <link>https://medium.com/@Raulgzm/securing-golang-api-using-json-web-token-jwt-2dc363792a48?source=rss-71d55c8ad440------2</link>
            <guid isPermaLink="false">https://medium.com/p/2dc363792a48</guid>
            <category><![CDATA[jwt]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[go]]></category>
            <dc:creator><![CDATA[Raúl González]]></dc:creator>
            <pubDate>Mon, 13 Nov 2017 17:19:27 GMT</pubDate>
            <atom:updated>2017-11-14T08:23:28.049Z</atom:updated>
            <content:encoded><![CDATA[<p>In this post, we will not only cover how to use Go to create a RESTful JSON API, but we will also describe how protect our API with JSON Web Tokens (JWT).</p><h3>What is JSON Web Token (JWT)</h3><p>According to the official site (<a href="http://jwt.io/">http://jwt.io/</a>):</p><p>JSON Web Token (JWT) is a compact URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is digitally signed using JSON Web Signature (JWS).</p><p>JWT consists of three main components: a header object, a claims object, and a signature. These three properties are encoded using base64, then concatenated with periods as separators.</p><p>The JWT claims object contains security information about the message. For example:</p><ol><li><strong>iss</strong>. Is the issuer of the claim. Connect uses it to identify the application making the call.</li><li><strong>iat</strong>. Issued-at time. Contains the UTC Unix time at which this token was issued. There are no hard requirements around this claim but it does not make sense for it to be significantly in the future. Also, significantly old issued-at times may indicate the replay of suspiciously old tokens.</li><li><strong>sub</strong>. The subject of this token. This is the user associated with the relevant action, and may not be present if there is no logged in user.</li></ol><h3>Authentication with JWT</h3><p>JSON Web Tokens (JWT) are a more modern approach to authentication. As the web moves to a greater separation between the client and server, JWT provides a wonderful alternative to traditional cookie based authentication models.</p><p>JWTs provide a way for clients to authenticate every request without having to maintain a session or repeatedly pass login credentials to the server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/1*iR3aP6QPoByZbypgQst6Yw.png" /><figcaption>Token-Based Auth</figcaption></figure><h3>Benefits of using a token-based approach</h3><ul><li><strong>Cross-domain / CORS</strong>: cookies + CORS don’t play well across different domains. A token-based approach allows you to make AJAX calls to any server, on any domain because you use an HTTP header to transmit the user information.</li><li><strong>Stateless</strong>: there is no need to keep a session store, the token is a self-contained entity that conveys all the user information.</li><li><strong>CDN</strong>: you can serve all the assets of your app from a CDN (e.g. javascript, HTML, images, etc.), and your server side is just the API.</li><li><strong>Decoupling</strong>: you are not tied to a particular authentication scheme. The token might be generated anywhere, hence your API can be called from anywhere with a single way of authenticating those calls.</li><li><strong>Mobile ready</strong>: when you start working on a native platform (iOS, Android, Windows 8, etc.) cookies are not ideal when consuming a secure API (you have to deal with cookie containers). Adopting a token-based approach simplifies this a lot.</li><li><strong>CRSF</strong>: since you are not relying on cookies, you don’t need to protect against cross site requests.</li></ul><h3>Organizing our Application code</h3><p>Why modular? Having all of our functionality in different modules helps us in many ways:</p><ol><li>The overall application layout is easier to understand.</li><li>You can see how the parts work together since modules have to be injected before use.</li><li>Code is reusable since all of the necessary functionality is contained inside the module.</li><li>Testing your code is much easier.</li></ol><p>Here is how we want our file structure to look like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*95ClxyNIeVzksZlVMFASYw.png" /></figure><h3>Creating Routers</h3><p>The code shown below creates a router assigning each route with his controller who runs when that endpoint is called.</p><p><strong>routers/router.go</strong></p><pre>package routers</pre><pre>import (<br>    &quot;github.com/gorilla/mux&quot;<br>)<br>func InitRoutes() *mux.Router {<br>    router := mux.NewRouter()<br>    router = SetHelloRoutes(router)<br>    router = SetAuthenticationRoutes(router)<br>    return router<br>}</pre><p><strong>routers/authentication.go</strong></p><pre>package routers</pre><pre>import (<br>    &quot;api.jwt.auth/controllers&quot;<br>    &quot;api.jwt.auth/core/authentication&quot;<br>    &quot;github.com/codegangsta/negroni&quot;<br>    &quot;github.com/gorilla/mux&quot;<br>)</pre><pre>func SetAuthenticationRoutes(router *mux.Router) *mux.Router {<br>    router.HandleFunc(<br>        &quot;/token-auth&quot;, <br>        controllers.Login<br>    ).Methods(&quot;POST&quot;)<br>    <br>    router.Handle(<br>        &quot;/refresh-token-auth&quot;,<br>        negroni.New(<br>            negroni.HandlerFunc(controllers.RefreshToken),<br>        )).Methods(&quot;GET&quot;)<br>    <br>    router.Handle(<br>        &quot;/logout&quot;,<br>        negroni.New(<br>            negroni.HandlerFunc(<br>                authentication.RequireTokenAuthentication<br>            ),<br>            negroni.HandlerFunc(controllers.Logout),<br>        )).Methods(&quot;GET&quot;)<br>    return router<br>}</pre><p><strong>routers/hello.go</strong></p><pre>package routers</pre><pre>import (<br>    &quot;api.jwt.auth/controllers&quot;<br>    &quot;api.jwt.auth/core/authentication&quot;<br>    &quot;github.com/codegangsta/negroni&quot;<br>    &quot;github.com/gorilla/mux&quot;<br>)</pre><pre>func SetHelloRoutes(router *mux.Router) *mux.Router {<br>    router.Handle(<br>        &quot;/test/hello&quot;,<br>        negroni.New(<br>            negroni.HandlerFunc(controllers.HelloController),<br>        )).Methods(&quot;GET&quot;)<br>    <br>    return router<br>}</pre><p><strong>Creating Controllers</strong></p><p>Let’s create our controller’s package to manage requests and responses. Controllers will interact with our services.</p><p><strong>controllers/auth_controller.go</strong></p><pre>package controllers</pre><pre>import (<br> &quot;api.jwt.auth/services&quot;<br> &quot;api.jwt.auth/services/models&quot;<br> &quot;encoding/json&quot;<br> &quot;net/http&quot;<br>)</pre><pre>func Login(w http.ResponseWriter, r *http.Request) {<br> requestUser := new(models.User)<br> decoder := json.NewDecoder(r.Body)<br> decoder.Decode(&amp;requestUser)</pre><pre>responseStatus, token := services.Login(requestUser)<br> w.Header().Set(&quot;Content-Type&quot;, &quot;application/json&quot;)<br> w.WriteHeader(responseStatus)<br> w.Write(token)<br>}</pre><pre>func RefreshToken(w http.ResponseWriter, r *http.Request, next http.HandlerFunc) {<br> requestUser := new(models.User)<br> decoder := json.NewDecoder(r.Body)<br> decoder.Decode(&amp;requestUser)</pre><pre>w.Header().Set(&quot;Content-Type&quot;, &quot;application/json&quot;)<br> w.Write(services.RefreshToken(requestUser))<br>}</pre><pre>func Logout(w http.ResponseWriter, r *http.Request, next http.HandlerFunc) {<br> err := services.Logout(r)<br> w.Header().Set(&quot;Content-Type&quot;, &quot;application/json&quot;)<br> if err != nil {<br>  w.WriteHeader(http.StatusInternalServerError)<br> } else {<br>  w.WriteHeader(http.StatusOK)<br> }<br>}</pre><p><strong>controllers/hello_controller.go</strong></p><pre>package controllers</pre><pre>import (<br> &quot;net/http&quot;<br>)</pre><pre>func HelloController(w http.ResponseWriter, r *http.Request, next http.HandlerFunc) {<br> w.Write([]byte(&quot;Hello, World!&quot;))<br>}</pre><p><strong>Creating models</strong></p><p>Now that we have routes and controllers in place, it’s time to create a basic user model that we can use to authenticate requests.</p><p><strong>services/models/users.go</strong></p><pre>package models</pre><pre>type User struct {<br> UUID     string `json:&quot;uuid&quot; form:&quot;-&quot;`<br> Username string `json:&quot;username&quot; form:&quot;username&quot;`<br> Password string `json:&quot;password&quot; form:&quot;password&quot;`<br>}</pre><p><strong>Creating Services</strong></p><p><strong>services/auth_service.go</strong></p><pre>package services</pre><pre>import (<br> &quot;api.jwt.auth/api/parameters&quot;<br> &quot;api.jwt.auth/core/authentication&quot;<br> &quot;api.jwt.auth/services/models&quot;<br> &quot;encoding/json&quot;<br> jwt &quot;github.com/dgrijalva/jwt-go&quot;<br> &quot;net/http&quot;<br>)</pre><pre>func Login(requestUser *models.User) (int, []byte) {<br> authBackend := authentication.InitJWTAuthenticationBackend()</pre><pre>if authBackend.Authenticate(requestUser) {<br>  token, err := authBackend.GenerateToken(requestUser.UUID)<br>  if err != nil {<br>   return http.StatusInternalServerError, []byte(&quot;&quot;)<br>  } else {<br>   response, _ := json.Marshal(parameters.TokenAuthentication{token})<br>   return http.StatusOK, response<br>  }<br> }</pre><pre>return http.StatusUnauthorized, []byte(&quot;&quot;)<br>}</pre><pre>func RefreshToken(requestUser *models.User) []byte {<br> authBackend := authentication.InitJWTAuthenticationBackend()<br> token, err := authBackend.GenerateToken(requestUser.UUID)<br> if err != nil {<br>  panic(err)<br> }<br> response, err := json.Marshal(parameters.TokenAuthentication{token})<br> if err != nil {<br>  panic(err)<br> }<br> return response<br>}</pre><pre>func Logout(req *http.Request) error {<br> authBackend := authentication.InitJWTAuthenticationBackend()<br> tokenRequest, err := jwt.ParseFromRequest(req, func(token *jwt.Token) (interface{}, error) {<br>  return authBackend.PublicKey, nil<br> })<br> if err != nil {<br>  return err<br> }<br> tokenString := req.Header.Get(&quot;Authorization&quot;)<br> return authBackend.Logout(tokenString, tokenRequest)<br>}</pre><p><strong>Web server</strong></p><pre>package main</pre><pre>import (<br> &quot;api.jwt.auth/routers&quot;<br> &quot;api.jwt.auth/settings&quot;<br> &quot;github.com/codegangsta/negroni&quot;<br> &quot;net/http&quot;<br>)</pre><pre>func main() {<br> settings.Init()<br> router := routers.InitRoutes()<br> n := negroni.Classic()<br> n.UseHandler(router)<br> http.ListenAndServe(&quot;:5000&quot;, n)<br>}</pre><p><strong>Let’s try our luck!</strong></p><p>If we try to test it, we will obtain a valid response from server:</p><p>![](/content/images/2015/05/curl_valid_response-1.png)</p><p>![](/content/images/2015/05/web_valid_response.png)</p><p>At this moment we have not needed to send a valid token to the server to obtain a valid response</p><h3>Applying authentication with JWT</h3><p>As we can see right now, our API endpoint ”/test/hello” is insecure. Let’s add our “RequireTokenAuthentication” middleware to protect it.</p><p><strong>core/authentication/middlewares.go</strong></p><pre>package authentication</pre><pre>import (<br> &quot;fmt&quot;<br> jwt &quot;github.com/dgrijalva/jwt-go&quot;<br> &quot;net/http&quot;<br>)</pre><pre>func RequireTokenAuthentication(rw http.ResponseWriter, req *http.Request, next http.HandlerFunc) {<br> authBackend := InitJWTAuthenticationBackend()</pre><pre>token, err := jwt.ParseFromRequest(req, func(token *jwt.Token) (interface{}, error) {<br>  if _, ok := token.Method.(*jwt.SigningMethodRSA); !ok {<br>   return nil, fmt.Errorf(&quot;Unexpected signing method: %v&quot;, token.Header[&quot;alg&quot;])<br>  } else {<br>   return authBackend.PublicKey, nil<br>  }<br> })</pre><pre>if err == nil &amp;&amp; token.Valid &amp;&amp; !authBackend.IsInBlacklist(req.Header.Get(&quot;Authorization&quot;)) {<br>  next(rw, req)<br> } else {<br>  rw.WriteHeader(http.StatusUnauthorized)<br> }<br>}</pre><p><strong>routers/hello.go</strong></p><pre>package routers</pre><pre>import (<br> &quot;api.jwt.auth/controllers&quot;<br> &quot;api.jwt.auth/core/authentication&quot;<br> &quot;github.com/codegangsta/negroni&quot;<br> &quot;github.com/gorilla/mux&quot;<br>)</pre><pre>func SetHelloRoutes(router *mux.Router) *mux.Router {<br> router.Handle(&quot;/test/hello&quot;,<br>  negroni.New(<br>   negroni.HandlerFunc(authentication.RequireTokenAuthentication),<br>   negroni.HandlerFunc(controllers.HelloController),<br>  )).Methods(&quot;GET&quot;)</pre><pre> return router<br>}</pre><p>Now, our API test endpoint is secured and it’s necessary a valid token to obtain a valid response.</p><h3>Let’s try our luck again!</h3><p>If we can try again without a valid token, we’ll receive a unauthorized error response:</p><p>![](/content/images/2015/05/curl_unauthorized.png)\n\n</p><p><strong>…for the last time!</strong></p><p>if we add an authorization header to our request we’ll obtain a valid response from the server:\n\n1. Firstly we need to obtain a valid token:</p><p>![](/content/images/2015/05/login.png)\n2.</p><p>Finally, we can do the request with our valid token:</p><p>![](/content/images/2015/05/valid_request-1.png)</p><h3>Session control &amp; Token Logout</h3><p>The last step, or bonus step, is how we can manage user logout and invalidate his token.</p><p>Imagine that an user token has been captured from third party or simply an user wants to logout from a client and we don’t want his token to be valid again. In this way, we force he to do login again for security reasons.</p><p>To solve this problems, we’ll use Redis to store all invalid tokens until their expiration.</p><p>For that, we need the methods: Logout and IsInBlacklist. The first method sets token’s value in Redis with his expiration and the second method checks if a token is stored in redis\n\n</p><p><strong>core/authentication/jwt_backend.go</strong></p><pre>package authentication</pre><pre>import (<br>    &quot;api.jwt.auth/core/redis&quot;<br>    &quot;api.jwt.auth/services/models&quot;<br>    &quot;api.jwt.auth/settings&quot;<br>    &quot;bufio&quot;<br>    &quot;code.google.com/p/go-uuid/uuid&quot;<br>    &quot;crypto/rsa&quot;<br>    &quot;crypto/x509&quot;<br>    &quot;encoding/pem&quot;<br>    jwt &quot;github.com/dgrijalva/jwt-go&quot;<br>    &quot;golang.org/x/crypto/bcrypt&quot;<br>    &quot;os&quot;<br>    &quot;time&quot;<br>)</pre><pre>type JWTAuthenticationBackend struct {<br>    privateKey *rsa.PrivateKey<br>    PublicKey  *rsa.PublicKey<br>}</pre><pre>const (<br>    tokenDuration = 72<br>    expireOffset  = 3600<br>)</pre><pre>var authBackendInstance *JWTAuthenticationBackend = nil</pre><pre>func InitJWTAuthenticationBackend() *JWTAuthenticationBackend {<br>    if authBackendInstance == nil {<br>        authBackendInstance = &amp;JWTAuthenticationBackend{<br>            privateKey: getPrivateKey(),<br>            PublicKey:  getPublicKey(),<br>        }<br>    }<br>    <br>    return authBackendInstance<br>}</pre><pre>func (backend *JWTAuthenticationBackend) GenerateToken(userUUID string) (string, error) {<br>    token := jwt.New(jwt.SigningMethodRS512)<br>    token.Claims[&quot;exp&quot;] = time.Now().Add(time.Hour * time.Duration(settings.Get().JWTExpirationDelta)).Unix()<br>    token.Claims[&quot;iat&quot;] = time.Now().Unix()<br>    token.Claims[&quot;sub&quot;] = userUUID<br>    tokenString, err := token.SignedString(backend.privateKey)<br>    if err != nil {<br>        panic(err)<br>        return &quot;&quot;, err<br>    }<br>    return tokenString, nil<br>}</pre><pre>func (backend *JWTAuthenticationBackend) Authenticate(user *models.User) bool {<br>    hashedPassword, _ := bcrypt.GenerateFromPassword([]byte(&quot;testing&quot;), 10)<br>    <br>    testUser := models.User{<br>        UUID:     uuid.New(),<br>        Username: &quot;haku&quot;,<br>        Password: string(hashedPassword),<br>    }<br>    <br>    return user.Username == testUser.Username &amp;&amp; bcrypt.CompareHashAndPassword([]byte(testUser.Password), []byte(user.Password)) == nil<br>}</pre><pre>func (backend *JWTAuthenticationBackend) getTokenRemainingValidity(timestamp interface{}) int {<br>    if validity, ok := timestamp.(float64); ok {<br>        tm := time.Unix(int64(validity), 0)<br>        remainer := tm.Sub(time.Now())<br>        if remainer &gt; 0 {<br>            return int(remainer.Seconds() + expireOffset)<br>        }<br>    }<br>    return expireOffset<br>}</pre><pre>func (backend *JWTAuthenticationBackend) Logout(tokenString string, token *jwt.Token) error {<br>    redisConn := redis.Connect()<br>    return redisConn.SetValue(tokenString, tokenString, backend.getTokenRemainingValidity(token.Claims[&quot;exp&quot;]))<br>}</pre><pre>func (backend *JWTAuthenticationBackend) IsInBlacklist(token string) bool {<br>    redisConn := redis.Connect()<br>    redisToken, _ := redisConn.GetValue(token)<br>    <br>    if redisToken == nil {<br>        return false<br>    }<br>    <br>    return true<br>}</pre><pre>func getPrivateKey() *rsa.PrivateKey {<br>    privateKeyFile, err := os.Open(settings.Get().PrivateKeyPath)<br>    if err != nil {<br>        panic(err)<br>    }<br>    <br>    pemfileinfo, _ := privateKeyFile.Stat()<br>    var size int64 = pemfileinfo.Size()<br>    pembytes := make([]byte, size)<br>    <br>    buffer := bufio.NewReader(privateKeyFile)<br>    _, err = buffer.Read(pembytes)<br>    <br>    data, _ := pem.Decode([]byte(pembytes))<br>    <br>    privateKeyFile.Close()<br>    <br>    privateKeyImported, err := x509.ParsePKCS1PrivateKey(data.Bytes)<br>    <br>    if err != nil {<br>        panic(err)<br>    }<br>    <br>    return privateKeyImported<br>}</pre><pre>func getPublicKey() *rsa.PublicKey {<br>    publicKeyFile, err := os.Open(settings.Get().PublicKeyPath)<br>    if err != nil {<br>        panic(err)<br>    }<br>    <br>    pemfileinfo, _ := publicKeyFile.Stat()<br>    var size int64 = pemfileinfo.Size()<br>    pembytes := make([]byte, size)<br>    <br>    buffer := bufio.NewReader(publicKeyFile)<br>    _, err = buffer.Read(pembytes)<br>    <br>    data, _ := pem.Decode([]byte(pembytes))<br>    <br>    publicKeyFile.Close()<br>    <br>    publicKeyImported, err := x509.ParsePKIXPublicKey(data.Bytes)<br>    <br>    if err != nil {<br>        panic(err)<br>    }<br>    <br>    rsaPub, ok := publicKeyImported.(*rsa.PublicKey)<br>    <br>    if !ok {<br>        panic(err)<br>    }<br>    <br>    return rsaPub<br>}</pre><p><strong>services/auth_services.go</strong></p><pre>func Logout(req *http.Request) error {<br>    authBackend := authentication.InitJWTAuthenticationBackend()<br>    tokenRequest, err := jwt.ParseFromRequest(req, func(token *jwt.Token) (interface{}, error) {<br>        return authBackend.PublicKey, nil<br>    })<br>    if err != nil {<br>        return err<br>    }<br>    tokenString := req.Header.Get(&quot;Authorization&quot;)<br>    return authBackend.Logout(tokenString, tokenRequest)<br>}</pre><h3><strong>Can I get all the code?</strong></h3><p>Yes! of course. Here is a repo with all of the code and tests.</p><p><a href="https://github.com/brainattica/golang-jwt-authentication-api-sample/n/n">https://github.com/brainattica/golang-jwt-authentication-api-sample</a></p><h3>Summary</h3><p>That’s all you have to do. JWT is a fantastic and simple way to communicate trusted information across untrusted channels. Hope you find a good use for it soon!</p><p>As well as I hope you found this post useful and helped you.</p><p>&gt; Code less, compile quicker &amp; execute faster</p><p>have more fun!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2dc363792a48" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Golang & Cryptography. RSA asymmetric algorithm]]></title>
            <link>https://medium.com/@Raulgzm/golang-cryptography-rsa-asymmetric-algorithm-e91363a2f7b3?source=rss-71d55c8ad440------2</link>
            <guid isPermaLink="false">https://medium.com/p/e91363a2f7b3</guid>
            <category><![CDATA[rsa]]></category>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[cryptography]]></category>
            <dc:creator><![CDATA[Raúl González]]></dc:creator>
            <pubDate>Sun, 25 Jun 2017 08:13:02 GMT</pubDate>
            <atom:updated>2017-06-25T08:28:04.687Z</atom:updated>
            <content:encoded><![CDATA[<p>RSA is a cryptosystem for public-key encryption, and is widely used for securing sensitive data, particularly when being sent over an insecure network such as the Internet.</p><p>As we said all of the major cryptographic libraries are often written in C (or in C++). GO is quite C-like in spirit, being a small and efficient language with convenient low-level facilities such as pointers. Yet Go also offers many features associated with high- or very high-level languages. Go philosphy is “Code less, compile quicker, execute faster”.</p><p>All of this makes it a good choice for Cryptography applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*_8ethuqFdCeJgK0vpcDmTQ.png" /></figure><p>In this small example, I’ll show you how to use each of the functions listed in the crypto/rsa package to send, receive and verify a secret message.</p><p>Maria wants to send a secret message to me, but I need verify that original sender was Maria and can read in plain text the message. OK! we already have our goal.</p><p>OK! let’s go to start on a good foot. The first task is create one RSA key pair to Maria and another pair to me.</p><pre>import (<br>    &quot;crypto&quot;<br>    &quot;crypto/rand&quot;<br>    &quot;crypto/rsa&quot;<br>    &quot;crypto/sha256&quot;<br>    &quot;fmt&quot;<br>    &quot;os&quot;<br>)</pre><pre>mariaPrivateKey, err := rsa.GenerateKey(rand.Reader, 2048)</pre><pre>if err != nil {<br>    fmt.Println(err.Error)<br>    os.Exit(1)<br>}</pre><pre>mariaPublicKey := &amp;miryanPrivateKey.PublicKey</pre><pre>raulPrivateKey, err := rsa.GenerateKey(rand.Reader, 2048)</pre><pre>if err != nil {<br>    fmt.Println(err.Error)<br>    os.Exit(1)<br>}</pre><pre>raulPublicKey := &amp;raulPrivateKey.PublicKey</pre><pre>fmt.Println(&quot;Private Key : &quot;, mariaPrivateKey)<br>fmt.Println(&quot;Public key &quot;, mariaPublicKey)<br>fmt.Println(&quot;Private Key : &quot;, raulPrivateKey)<br>fmt.Println(&quot;Public key &quot;, raulPublicKey)</pre><p>Firstly she should encrypts her message with the Raul’s public key to send it encrypted.</p><pre>message := []byte(&quot;the code must be like a piece of music&quot;)<br>label := []byte(&quot;&quot;)<br>hash := sha256.New()</pre><pre>ciphertext, err := rsa.EncryptOAEP(<br>    hash, <br>    rand.Reader, <br>    raulPublicKey, <br>    message, <br>    label<br>)</pre><pre>if err != nil {<br>    fmt.Println(err)<br>    os.Exit(1)<br>}</pre><pre>fmt.Printf(&quot;OAEP encrypted [%s] to \n[%x]\n&quot;, string(message), ciphertext)</pre><blockquote>OAEP is the recommended padding choice for encryption for new protocols or applications. PKCS1v15 should only be used to support legacy protocols.</blockquote><p>3. Next Maria should signs her message with her private key to ensure the recipient can verify the message sender to confirm the sender.</p><pre>var opts rsa.PSSOptions<br>opts.SaltLength = rsa.PSSSaltLengthAuto // for simple example<br>PSSmessage := message<br>newhash := crypto.SHA256<br>pssh := newhash.New()<br>pssh.Write(PSSmessage)<br>hashed := pssh.Sum(nil)</pre><pre>signature, err := rsa.SignPSS(<br>    rand.Reader, <br>    mariaPrivateKey, <br>    newhash, <br>    hashed, <br>    &amp;opts<br>)</pre><pre>if err != nil {<br>    fmt.Println(err)<br>    os.Exit(1)<br>}</pre><pre>fmt.Printf(&quot;PSS Signature : %x\n&quot;, signature)</pre><blockquote>PSS algorithm is the recommended padding choice for any new protocols or applications, PKCS1v15 should only be used to support legacy protocols.</blockquote><p>4. Maria has everything she needs to send her secret message to me now:</p><p>[ciphertext, signature]</p><p>5. When I receive Maria’s message the first thing I’ll do will be decrypt the message:</p><pre>plainText, err := rsa.DecryptOAEP(<br>    hash, <br>    rand.Reader, <br>    raulPrivateKey, <br>    ciphertext, <br>    label<br>)</pre><pre>if err != nil {<br>    fmt.Println(err)<br>    os.Exit(1)<br>}</pre><pre>fmt.Printf(&quot;OAEP decrypted [%x] to \n[%s]\n&quot;, ciphertext, plainText)</pre><p>6. Last resort, I should verify the message origin to determine it is Maria:</p><pre>err = rsa.VerifyPSS(<br>    mariaPublicKey, <br>    newhash, <br>    hashed, <br>    signature, <br>    &amp;opts<br>)</pre><pre>if err != nil {<br>    fmt.Println(&quot;Who are U? Verify Signature failed&quot;)<br>    os.Exit(1)<br>} else {<br>    fmt.Println(&quot;Verify Signature successful&quot;)<br>}</pre><p>Finally, I have got my message sent by Maria and I could verify the message is authentic. I’m not able to hide my joy!</p><p>I find interesting GO as an awesome programming language. I love GO and his philosophy:</p><blockquote>“Code less, compile quicker, execute faster”</blockquote><p>I hope this article was of some use to you. Please let me know if you have any questions or suggestions for improvement.</p><p>Have fun!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e91363a2f7b3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>