small grammar

calcode · calcode · commit 59a60b58cf45 · 2024-12-15T23:37:02.000Z
diff --git a/_posts/2014-09-15-hello-jekyll.md b/_posts/2014-09-15-hello-jekyll.md
@@ -6,12 +6,12 @@ permalink: wordpress-jekyll/
 
 Goodbye [WordPress](http://www.wordpress.org/). It's been great working with you! Hello, [Jekyll](http://jekyllrb.com). Jekyll is a static site generator and an open-source tool for creating simple yet powerful websites of all shapes and sizes. To quote [the project's readme](https://github.com/jekyll/jekyll/blob/master/README.markdown):
 
-> Jekyll is a simple, blog aware, static site generator. It takes a template directory [...] and spits out a complete, static website suitable for serving with Apache or your favorite web server. This is also the engine behind GitHub Pages, which you can use to host your project’s page or blog right here from GitHub.
+> Jekyll is a simple, blog aware, static site generator. It takes a template directory [...] and spits out a complete, static website suitable for serving with Apache or your favorite web server. This is also the engine behind GitHub Pages, which you can use to host your project’s page or blog right here from GitHub
 
-[GitHub](https://github.com/) you say? Sounds good to me. 
+[GitHub](https://github.com/) you say? Sounds good to me.
 
 We're now up and running on GitHub, with Poole as our chosen template for Jekyll.
 
 Migrating from WordPress is a breeze with some of the helpful apps available for this exact purpose. Interested? Check out this great post by [leon Paternoster](http://www.leonpaternoster.com/2013/06/moving-from-wordpress-to-jekyll/) for a detailed guide.  
 
-If you're less familiar with coding, there's a handy Windows app that does the job in a flash:[wpXml2Jekyll](https://github.com/theaob/wpXml2Jekyll). You can grab it on GitHub.
+If you're less familiar with coding, there's a handy Windows app that does the job in a flash:[wpXml2Jekyll](https://github.com/theaob/wpXml2Jekyll). You can grab it on GitHub.
diff --git a/_posts/2015-12-28-assumed-facts-educated-decisions.md b/_posts/2015-12-28-assumed-facts-educated-decisions.md
@@ -6,29 +6,29 @@ permalink: assumed-facts-educated-decisions/
 
 I love the [definition of data provided by Google](https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=data%20definition):  
 
-> Data, in philosophy, is “things known or assumed as facts, making the basis of reasoning or calculation.”
+> Data, in philosophy, is “things known or assumed as facts, making the basis of reasoning or calculation”
 
-There’s something inherently beautiful about this definition. It establishes a relationship between assumed facts and their role in reasoning—ultimately enabling us to make educated decisions. 
+There’s something inherently beautiful about this definition. It establishes a relationship between assumed facts and their role in reasoning—ultimately enabling us to make educated decisions.
 
 [Reasoning](https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=reasoning+definition), in turn, is defined as:  
 
-> “The action of thinking about something in a logical, sensible way.”
+> “The action of thinking about something in a logical, sensible way”
 
-We know that data is fundamental to effective [user-centered design](https://en.wikipedia.org/wiki/User-centered_design). However, using the *wrong* data can sometimes be worse than having no data at all. Incorrect data can support flawed decisions and remain unnoticed for a long time. When we rely on flawed data to create solutions, we risk falling into a cycle of uneducated change—the exact opposite of what we aim to achieve through true iteration.  
+We know that data is fundamental to effective [user-centered design](https://en.wikipedia.org/wiki/User-centered_design). However, using the wrong data can sometimes be worse than having no data at all. Incorrect data can support flawed decisions and remain unnoticed for a long time. When we rely on flawed data to create solutions, we risk falling into a cycle of uneducated change, which is the exact opposite of what we aim to achieve through true iteration.
 
 > [Change](https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=definition%20of%20change):  
-> "An act or process through which something becomes different."
+> "An act or process through which something becomes different"
 
 Whereas:  
 
 > [Iteration](https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=iteration+definition):  
-> "The repetition of a process or utterance as a means of obtaining successively closer approximations to achieve a solution."
+> "The repetition of a process or utterance as a means of obtaining successively closer approximations to achieve a solution"
 
 To truly improve, we need to iterate. And iteration only works when we use the right data at the right time. Our methods should provide data that fuels reasoning and informs decision-making—not lead us astray.  
 
 ## The Importance of Context in Data
 
-Understanding and predicting user behavior is challenging even in the best of circumstances. This is why it's crucial to understand the available methods, what they provide, and how to converge data meaningfully.  
+Understanding and predicting user behaviour is challenging even in the best of circumstances. This is why it's crucial to understand the available methods, what they provide, and how to converge data meaningfully.  
 
 For example, pulling numbers from Google Analytics is meaningless without context. Context might come from additional sources, such as user interviews, or even understanding whether filters have been applied to the data. Beyond knowing *what* users are doing, context helps us uncover *why* they are doing it.
 
@@ -46,6 +46,6 @@ The goal is to present a series of assumed facts that enable us to make better-e
 
 ## Final Thoughts
 
-I have a feeling my phrase of the year for 2016 will be *assumed facts*—a reminder to base decisions on sound reasoning and reliable data.  
+I have a feeling my notes will have assumed facts there at the top, acting as a reminder to base decisions on sound reasoning and reliable data.  
 
-*Have a great New Year!*
+*Have a great New Year!*
diff --git a/_posts/2017-07-17-mapping-information-architecture.md b/_posts/2017-07-17-mapping-information-architecture.md
@@ -20,18 +20,16 @@ With MindNode, you can easily add nodes as new information or topics emerge from
 
 Here are some tips for creating effective IA diagrams with MindNode:
 
-- **Line Colours**: Use different colours to separate topics or highlight different audiences.
-- **Line Weightings**: Adjust line thickness to indicate the volume or complexity of the information.
-- **Arrows**: Use arrows to show relationships between nodes or highlight critical cross-linking.
-- **Node Types**: Represent the type of content (e.g., video, image, text) with specific node styles.
-- **Notes**: Add explanations to indicate where the information came from, such as user research findings.
+- Line Colours. Use different colours to separate topics or highlight different audiences.
+- Line Weightings. Adjust line thickness to indicate the volume or complexity of the information.
+- Arrows. Use arrows to show relationships between nodes or highlight critical cross-linking.
+- Node Types. Represent the type of content (e.g., video, image, text) with specific node styles.
+- Notes. Add explanations to indicate where the information came from, such as user research findings.
 
 You can also create a couple of main nodes to act as a legend, providing a clear reference for others viewing the diagram.
 
 MindNode is flexible enough to accommodate changes. If you need to move or reorganise elements, the nodes will dynamically adjust and resize. It’s intentionally vague enough to avoid being mistaken for a final deliverable, while still being clear and collaborative.
 
 For more on information architecture, check out [The Ultimate Guide to Information Architecture](https://www.webdesignerdepot.com/2015/02/the-ultimate-guide-to-information-architecture/) on Web Designer Depot.
 
-![](/content/images/2017/07/website-information-architecture.png)
-
 Give it a try and let me know how you get on!
diff --git a/_posts/2021-01-11-reading-suggestions-2021.md b/_posts/2021-01-11-reading-suggestions-2021.md
@@ -22,4 +22,4 @@ Roman Pichler’s previous book, *Strategize*, was a fantastic introduction to c
 - **[User Story Mapping: Discover the Whole Story, Build the Right Product](https://www.amazon.co.uk/User-Story-Mapping-Discover-Product-ebook/dp/B00NF07FHS/ref=sr_1_1?dchild=1&keywords=User+Story+Mapping_+Discover+the+Whole+Story%2C+Build+the+Right+Product&qid=1610391398&s=digital-text&sr=1-1)**  
 Jeff Patton is a well-known figure in the Agile community, and I’m embarrassed to admit I haven’t read this yet. After going remote, I stopped using story maps, which is a shame. It’s time to revisit this tool, and this book will help me do just that.
 
-- **[Forever Employable: How to Stop Looking for Work and Let Your Next Job Find You](https://www.amazon.co.uk/Forever-Employable-Stop-Looking-
+- **[Forever Employable: How to Stop Looking for Work and Let Your Next Job Find You](https://www.amazon.co.uk/Forever-Employable-Stop-Looking-Work/dp/B087D22VV3/ref=sr_1_1?crid=N9PI3LI57I4W&dib=eyJ2IjoiMSJ9.AnBJvEg6zdQ75TE8kkHwHq0xRWQka94DT43usIwt81Y.fdKRwbEYJ-1aLcGExY4pWw0iqoeYnDRyMP9YbZHViOM&dib_tag=se&keywords=forever+employable+stop+looking&nsdOptOutParam=true&qid=1734305445&sprefix=forever+employable+stop+looking%2Caps%2C100&sr=8-1)**
diff --git a/_posts/2022-02-17-product-roadmaps.md b/_posts/2022-02-17-product-roadmaps.md
@@ -53,7 +53,7 @@ We introduced several key changes to make the roadmap clearer and more actionabl
 - **Consistent granularity** between items to improve readability.  
 - **Links to opportunity assessments** for evaluating the value of ideas.  
 
-### Example internal roadmap:
+### Example internal roadmap
 
 [![13PrMX.md.png](https://iili.io/13PrMX.md.png)](https://freeimage.host/i/13PrMX)
 
diff --git a/_posts/2024-07-17-five-adages-product-managers.md b/_posts/2024-07-17-five-adages-product-managers.md
@@ -23,9 +23,9 @@ Let’s explore each one and how you can apply them in your role as a Product Ma
 This may sound gloomy, but I’ve found it to be a helpful mindset—especially after first hearing it in *Interstellar*.
 
 #### How to apply
-- **Expect Challenges:** Working in software means recognising that not everything is within your control. While you can manage certain aspects, you often depend on others (e.g., usable designs, reliable code) to ensure success.  
-- **Plan for Edge Cases:** Invest time in planning. Consider potential issues by discussing designs and implementations with engineers, always keeping the customer perspective in mind.  
-- **Stay Positive:** When things go wrong (and they will), approach problems with energy and positivity. Engage the right people to address the issue. View setbacks as opportunities to learn rather than as failures.
+- Expect Challenges. Working in software means recognising that not everything is within your control. While you can manage certain aspects, you often depend on others (e.g., usable designs, reliable code) to ensure success.  
+- Plan for Edge Cases. Invest time in planning. Consider potential issues by discussing designs and implementations with engineers, always keeping the customer perspective in mind.  
+- Stay Positive. When things go wrong (and they will), approach problems with energy and positivity. Engage the right people to address the issue. View setbacks as opportunities to learn rather than as failures.
 
 
 ### Gilbert’s Law
@@ -35,8 +35,8 @@ This may sound gloomy, but I’ve found it to be a helpful mindset—especially
 Fun fact: Gilbert also happens to be my father-in-law’s name!
 
 #### How to apply
-- **Be Organized:** As a Product Manager, it’s your job to bring structure to ambiguity. Before diving into new work, take a moment to map out what’s needed to move from problem to solution.  
-- **Communicate Clearly:** Whether you’re using formal product development principles or a simple checklist, create a plan and share it with the right stakeholders. The plan can take as little as five minutes to draft, but its impact will be significant.
+- Be Organised. As a Product Manager, it’s your job to bring structure to ambiguity. Before diving into new work, take a moment to map out what’s needed to move from problem to solution.  
+- Communicate Clearly. Whether you’re using formal product development principles or a simple checklist, create a plan and share it with the right stakeholders. The plan can take as little as five minutes to draft, but its impact will be significant.
 
 
 ### Kidlin’s Law
@@ -46,9 +46,9 @@ Fun fact: Gilbert also happens to be my father-in-law’s name!
 I’m not sure where this adage originates, but it’s one of my favourites.
 
 #### How to apply
-- **Define the Problem:** Writing a clear, succinct problem statement is one of the hardest—and most crucial—tasks in product development. A well-defined problem helps prevent teams from jumping to solutions prematurely.  
-- **Validate Understanding:** Replay the problem statement to your colleagues and customers. Is it specific? Is this the exact issue you want to solve?  
-- **Iterate Confidently:** Once you’ve nailed the problem, you can start exploring solutions. Expect to discover new insights along the way—that’s part of the process.
+- Define the Problem. Writing a clear, succinct problem statement is one of the hardest—and most crucial—tasks in product development. A well-defined problem helps prevent teams from jumping to solutions prematurely.  
+- Validate Understanding. Replay the problem statement to your colleagues and customers. Is it specific? Is this the exact issue you want to solve?  
+- Iterate Confidently. Once you’ve nailed the problem, you can start exploring solutions. Expect to discover new insights along the way—that’s part of the process.
 
 
 ### Wilson’s Law
@@ -58,8 +58,8 @@ I’m not sure where this adage originates, but it’s one of my favourites.
 This might sound counterintuitive at first, but there’s more to it than meets the eye.
 
 #### How to apply
-- **Focus on Growth:** Your value as a Product Manager increases with experience. Take on challenges that push you outside your comfort zone, and you’ll open doors to new opportunities.  
-- **Redefine Wealth:** Wealth isn’t just about money. Roles that emphasise the product and people can be deeply rewarding. Also, don’t forget to prioritise what truly matters—like family and personal time.
+- Focus on Growth. Your value as a Product Manager increases with experience. Take on challenges that push you outside your comfort zone, and you’ll open doors to new opportunities.  
+- Redefine Wealth. Wealth isn’t just about money. Roles that emphasise the product and people can be deeply rewarding. Also, don’t forget to prioritise what truly matters—like family and personal time.
 
 
 ### Falkland’s Law
@@ -69,4 +69,4 @@ This might sound counterintuitive at first, but there’s more to it than meets
 This adage is a game-changer for prioritisation.
 
 #### How to apply
-- **Stay Focused:** Once you’ve identified a specific problem, resist the temptation to tackle unrelated issues. Stay disciplined and solve the problem you set out to address.
+- Stay Focused. Once you’ve identified a specific problem, resist the temptation to tackle unrelated issues. Stay disciplined and solve the problem you set out to address.
