<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (earth2marsh)</title>
    <link>https://pinboard.in/u:earth2marsh/public/</link>
    <description>recent bookmarks from earth2marsh</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://oostkit.com/apps/intro_ost?from=section_theory"/>
	<rdf:li rdf:resource="https://nesbitt.io/2026/01/23/package-management-is-a-wicked-problem.html"/>
	<rdf:li rdf:resource="https://medium.com/@jakeorlowitz/the-most-predictable-edit-in-history-967956076b11"/>
	<rdf:li rdf:resource="https://merveilles.town/@lrhodes/116087470498684306"/>
	<rdf:li rdf:resource="https://www.linkedin.com/posts/johnpcutler_okrs-were-never-meant-to-solve-all-problems-activity-7347758036578390017-iL6r"/>
	<rdf:li rdf:resource="https://htmx.org/essays/vendoring/"/>
	<rdf:li rdf:resource="https://blog.danielna.com/vulnerability-avoidant/"/>
	<rdf:li rdf:resource="https://archive.ph/2024.12.01-042023/https://www.washingtonpost.com/wellness/2024/11/30/discomfort-grit-womens-soccer-coaching/"/>
	<rdf:li rdf:resource="https://www.figma.com/blog/welcome-to-the-wip/"/>
	<rdf:li rdf:resource="https://www.leadingsapiens.com/psychological-safety-vs-high-standards/"/>
	<rdf:li rdf:resource="https://zuplo.com/blog/2025/01/24/api-rate-limiting"/>
	<rdf:li rdf:resource="https://aeon.co/ideas/why-hiring-the-best-people-produces-the-least-creative-results"/>
	<rdf:li rdf:resource="https://landley.net/history/mirror/institutional_memory.html"/>
	<rdf:li rdf:resource="https://en.wikipedia.org/wiki/Parkinson%27s_law"/>
	<rdf:li rdf:resource="https://catswetel.com/blog/2021/5/4/an-extended-subtweet-on-power"/>
	<rdf:li rdf:resource="https://www.catharsisinsight.com/reports"/>
	<rdf:li rdf:resource="https://psychsafety.co.uk/the-seven-deadly-sins-of-psychological-safety/"/>
	<rdf:li rdf:resource="https://waysofworkingcollection.substack.com/p/okrs-arent-the-only-way-how-to-identify?triedRedirect=true"/>
	<rdf:li rdf:resource="https://skamille.medium.com/founders-create-managers-aba3c88981ba"/>
	<rdf:li rdf:resource="https://www.forrester.com/blogs/boomi-dismembers-the-tibco-frankenstein/"/>
	<rdf:li rdf:resource="https://www.youtube.com/watch?v=P4VBqTViEx4"/>
	<rdf:li rdf:resource="https://medium.com/@jurgenappelo/the-7-levels-of-delegation-672ec2a48103"/>
	<rdf:li rdf:resource="https://blog.appliedcomputing.io/p/okrs-are-bullshit"/>
	<rdf:li rdf:resource="https://www.rawsignal.ca/"/>
	<rdf:li rdf:resource="https://noidea.dog/glue"/>
	<rdf:li rdf:resource="https://randsinrepose.com/archives/shields-down/"/>
	<rdf:li rdf:resource="https://intenseminimalism.com/2015/a-framework-for-thinking-about-systems-change/"/>
	<rdf:li rdf:resource="https://faculty.haas.berkeley.edu/mhsu/blog/files/deming_measurement.html"/>
	<rdf:li rdf:resource="https://jacobian.org/2023/dec/1/against-rfcs/"/>
	<rdf:li rdf:resource="https://staysaasy.com/startups/2023/11/10/imprecise-asks.html"/>
	<rdf:li rdf:resource="https://hbr.org/2007/11/a-leaders-framework-for-decision-making"/>
	<rdf:li rdf:resource="https://everythingchanges.us/blog/energy-makes-time/"/>
	<rdf:li rdf:resource="https://knowyourteam.com/blog/2019/10/03/skip-level-meetings-what-they-are-and-exactly-how-to-run-them/"/>
	<rdf:li rdf:resource="https://news.ycombinator.com/item?id=25855303"/>
	<rdf:li rdf:resource="https://joshmcla.medium.com/manage-stakeholders-more-effectively-with-aai-not-raci-7982c79c8ba6"/>
	<rdf:li rdf:resource="https://chrisgagne.com/1255/mary-poppendiecks-the-tyranny-of-the-plan/"/>
	<rdf:li rdf:resource="https://medium.com/smells-like-team-spirit/should-management-be-on-your-career-path-a6aa6b7aad0a"/>
	<rdf:li rdf:resource="https://swiber.dev/future-of-api-management-in-2023-and-beyond"/>
	<rdf:li rdf:resource="https://blog.pragmaticengineer.com/project-management-at-big-tech/"/>
	<rdf:li rdf:resource="https://skamille.medium.com/opp-other-peoples-problems-d7eb174724ee"/>
	<rdf:li rdf:resource="https://www.industriallogic.com/blog/scatter-gather/"/>
	<rdf:li rdf:resource="https://www.svpg.com/coaching-tools-the-assessment/"/>
	<rdf:li rdf:resource="https://apenwarr.ca/log/20201227"/>
	<rdf:li rdf:resource="https://cutlefish.substack.com/p/20-things-ive-learned-as-a-systems?s=r"/>
	<rdf:li rdf:resource="https://dscout.com/people-nerds/organizational-trauma"/>
	<rdf:li rdf:resource="https://cdn.ymaws.com/www.tocico.org/resource/resmgr/2012_conf_pdfs/goldratt,_rami_management_at.pdf"/>
	<rdf:li rdf:resource="https://hbr.org/2020/11/how-apple-is-organized-for-innovation"/>
	<rdf:li rdf:resource="https://www.idevnews.com/stories/7509/API-Management-vs-Service-Mesh-The-Choice-Doesnt-Have-to-Be-Yours"/>
	<rdf:li rdf:resource="https://forcemultipliers.substack.com/p/setting-up-your-new-pm-hire-to-win?s=r"/>
	<rdf:li rdf:resource="https://qaspire.com/2022/01/10/conversations-that-build-psychological-safety/"/>
	<rdf:li rdf:resource="https://danluu.com/people-matter/"/>
	<rdf:li rdf:resource="https://basecamp.com/shapeup/webbook"/>
	<rdf:li rdf:resource="https://github.com/athensresearch/athens"/>
	<rdf:li rdf:resource="https://www.youtube.com/watch?v=YyXRYgjQXX0"/>
	<rdf:li rdf:resource="https://skamille.medium.com/an-incomplete-list-of-skills-senior-engineers-need-beyond-coding-8ed4a521b29f"/>
	<rdf:li rdf:resource="https://jamesclear.com/marginal-gains"/>
	<rdf:li rdf:resource="https://svpg.com/the-mba-pathology/"/>
	<rdf:li rdf:resource="https://www.thekua.com/atwork/2019/02/the-trident-model-of-career-development/"/>
	<rdf:li rdf:resource="https://newsletter.bringthedonuts.com/p/dual-product-management-career-path"/>
	<rdf:li rdf:resource="https://slate.com/news-and-politics/2002/04/an-ode-to-managers.html"/>
	<rdf:li rdf:resource="https://medium.learningbyshipping.com/reaching-peak-meeting-efficiency-f8e47c93317a"/>
	<rdf:li rdf:resource="https://boz.com/articles/mutual-knowledge"/>
	<rdf:li rdf:resource="https://medium.com/swlh/the-silent-meeting-manifesto-v1-189e9e3487eb"/>
	<rdf:li rdf:resource="https://www.thepirasgroup.com/blog/yes-and-versus-yes-but-can-dialog-be-this-simple"/>
	<rdf:li rdf:resource="https://queue.acm.org/detail.cfm?id=3454124"/>
	<rdf:li rdf:resource="https://hbr.org/2021/01/the-forgotten-dimension-of-diversity?s=09"/>
	<rdf:li rdf:resource="https://www.investopedia.com/terms/p/porter.asp"/>
	<rdf:li rdf:resource="https://www.nytimes.com/2019/03/28/smarter-living/productivity-isnt-about-time-management-its-about-attention-management.html"/>
	<rdf:li rdf:resource="https://exp-platform.com/hippo/"/>
	<rdf:li rdf:resource="http://www.zengestrom.com/blog/2012/09/21-characteristics-of-great-teams.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://oostkit.com/apps/intro_ost?from=section_theory">
    <title>Introduction to OST — OOSTKit</title>
    <dc:date>2026-06-29T06:47:52+00:00</dc:date>
    <link>https://oostkit.com/apps/intro_ost?from=section_theory</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Six criteria for productive work
Over decades of action research across dozens of countries, the Emerys identified six conditions that, when present, produce sustained motivation, learning, and genuine engagement at work. When they are absent, no amount of leadership training, culture work, or engagement programming compensates; the problems return. The six have now been measured in enough organisations, across enough cultures, that they appear to be a consistent feature of how human beings respond to work, not a product of any particular industry or context.

The first three concern the content of the work itself, and must be optimal for each person: neither too little nor too much. Too little and the work becomes stifling; too much and it becomes overwhelming. The right level varies between people and shifts over time.

Elbow room. People make real decisions about how their own work gets done. Not micromanaged, not left entirely at sea.
Continual learning. People set goals and get honest, timely feedback on whether they've been met. They can see themselves getting better.
Variety. The work has enough range to stay interesting and to call on different capabilities. Not so much that it fragments into chaos.
The second three concern the climate of the workplace. These have no upper limit; there is no such thing as too much of any of them.

Mutual support and respect. People help each other out without being asked, and can rely on the same in return. Nobody is left isolated when the work gets hard.
Meaningfulness. The work connects to something that matters beyond the immediate task. People can see the whole product or service they're contributing to, and feel it's worth having in the world.
A desirable future. The role leads somewhere. People are developing skills and taking on more responsibility over time, not repeating the same tasks indefinitely.
The critical point for practitioners is this: none of these six conditions can be reliably installed through training, coaching, or engagement programmes. They are produced (or destroyed) by the structure of the work itself.

DP1 removes them, one by one. Elbow room disappears when a manager makes the decisions. Continual learning stalls when jobs are simplified and feedback routes to the top. Mutual support erodes when people compete for promotion. Meaningfulness gets lost when nobody sees the whole. A desirable future becomes a management career path that most people can't access.</blockquote>]]></description>
<dc:subject>systems management organization OST</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:29acac2e4c5a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:systems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:organization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:OST"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://nesbitt.io/2026/01/23/package-management-is-a-wicked-problem.html">
    <title>Package Management is a Wicked Problem | Andrew Nesbitt</title>
    <dc:date>2026-06-20T03:00:34+00:00</dc:date>
    <link>https://nesbitt.io/2026/01/23/package-management-is-a-wicked-problem.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Rittel and Webber’s answer to wicked problems was participatory planning: bring stakeholders together early, iterate continuously, accept that you’re managing tradeoffs rather than finding solutions. If we accept that these problems are wicked, we stop looking for a perfect tool and start looking for better ways to communicate across tools. That shift from tools to interfaces is what led me to think about what a shared protocol for package management might look like.</blockquote>]]></description>
<dc:subject>systems package management problems</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:d9d4db607e0b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:systems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:package"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:problems"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/@jakeorlowitz/the-most-predictable-edit-in-history-967956076b11">
    <title>The Most Predictable Edit in History | by Jake Orlowitz | Jun, 2026 | Medium</title>
    <dc:date>2026-06-06T04:17:21+00:00</dc:date>
    <link>https://medium.com/@jakeorlowitz/the-most-predictable-edit-in-history-967956076b11</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>The recurring failure of centralized power is not that it cannot think. It is that it keeps mistaking the people who can see for the people who must be managed. The eyes are at the edge. They always have been.</blockquote>]]></description>
<dc:subject>wikipedia community Management mistakes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:6d729a9de3a3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:wikipedia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:community"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:Management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:mistakes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://merveilles.town/@lrhodes/116087470498684306">
    <title>Bookmarked toot from lrhodes</title>
    <dc:date>2026-02-18T08:41:55+00:00</dc:date>
    <link>https://merveilles.town/@lrhodes/116087470498684306</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[[NB: comment on appeal of LLMs and coding assistants to senior leadership management types]

I recall the childhood dopamine hit of playing with BASIC or Pascal, and getting this inscrutable machine to perform an action. That rush propelled a lot of my friends into CS degrees.

Over time, the rush was harder to get. You improve; the old challenges seem trivial; trivial doesn't deliver. My friends started to hate their jobs. Getting a response out of the abyss of the dimly understood… That was the magic.

When I see lifers getting sucked into vibecoding, that's what I assume they're after: the magic of being a pajama-clad 10 year-old coaxing a big beige box to bend to their will. No wonder they can't see it clearly.
mast-id:116087470617490893]]></description>
<dc:subject>masto-bmarks leadership management appeal LLMs assistants</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:d1222dd21237/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:masto-bmarks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:leadership"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:appeal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:LLMs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:assistants"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.linkedin.com/posts/johnpcutler_okrs-were-never-meant-to-solve-all-problems-activity-7347758036578390017-iL6r">
    <title>John Cutler - OKRs were never meant to solve all problems - Feed | LinkedIn</title>
    <dc:date>2025-07-08T23:43:49+00:00</dc:date>
    <link>https://www.linkedin.com/posts/johnpcutler_okrs-were-never-meant-to-solve-all-problems-activity-7347758036578390017-iL6r</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>OKRs were never meant to solve all problems. Each one of these "weaknesses" is an opportunity to mix in other tools/methods to supercharge OKRs. 

A quarter is an arbitrary duration
A quarter is an odd duration: too long to promote small, iterative work and too short for deep strategic focus.

No way to express uncertainty
There's no good way to express uncertainty, assumptions, or the need to learn. Teams feel pressure to sound confident. “Good” OKRs turn out overly certain and definitive.

OKRs emphasize vertical alignment, ignore horizontal progressions
The dominant linking model is vertical (e.g., supporting a higher-level OKR). This misses how one goal is a stepping stone in a broader progression.

No mechanism to reset goals mid-cycle
Many companies lack a process for revisiting and adjusting OKRs when conditions change. Teams try to force-fit progress to outdated plans.

Teams set goals against untested metrics
Many key metrics are poorly instrumented, poorly understood, or newly created. Setting goals against them can be premature and misleading without baseline understanding.

OKRs ignore how outcomes are achieved
The systems, habits, and approaches used to reach goals often matter as much as the outcomes themselves.

OKRs don’t express or guide relative prioritization
While you can try to infer what matters most, OKRs don’t explicitly convey relative importance or trade-offs between goals. They lack built-in prioritization logic.

OKRs ignore KTLO and BAU work
Keep-the-lights-on and business-as-usual work often isn’t reflected in OKRs. This creates confusion about where time went and can lead to unrealistic expectations around capacity.

OKRs structured by org chart mask real dependencies
When OKRs mirror the org chart, they create a false sense of independence. Teams may appear accountable in isolation, but in reality, progress depends on other groups (and those links often go unacknowledged).

OKRs create a double burden alongside actual work tracking
Teams still need to track and coordinate the work (tasks, deliverables, timelines, etc.) OKRs often live in a separate layer, leading to redundant effort and disconnects between goals and day-to-day work.

OKRs are tacked onto existing work
Rather than shaping priorities, OKRs are often retrofitted to projects teams already planned to do. This creates the illusion of focus without actually changing behavior or decision-making.

OKRs strip away context and narrative
OKRs are meant to be concise, but in doing so they often lose the story behind the work (why it matters, how it connects to other efforts, and what trade-offs are involved, etc.)</blockquote>]]></description>
<dc:subject>okrs productmanagement management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:2e9b7a21adb8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:okrs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://htmx.org/essays/vendoring/">
    <title>&lt;/&gt; htmx ~ Vendoring</title>
    <dc:date>2025-04-20T21:10:57+00:00</dc:date>
    <link>https://htmx.org/essays/vendoring/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>“Vendoring” software is a technique where you copy the source of another project directly into your own project.

It is an old technique that has been used for time immemorial in software development, but the term “vendoring” to describe it appears to have originated in the ruby community.

Vendoring can be and is still used today. You can vendor htmx, for example, quite easily.</blockquote>]]></description>
<dc:subject>dependencies management software opensource</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:96a2412f7140/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:dependencies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.danielna.com/vulnerability-avoidant/">
    <title>Vulnerability Avoidant | blog.danielna.com</title>
    <dc:date>2025-03-17T03:05:39+00:00</dc:date>
    <link>https://blog.danielna.com/vulnerability-avoidant/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Vulnerability isn’t nice or mean, it’s honest
When I use the word “vulnerable,” I don’t mean “meek” or “emotionally demonstrative.” You don’t have to have tears in your eyes to be vulnerable. In this context vulnerability means being willing to do the leg work to be emotionally and intellectually honest when evaluating a situation, and confront the truth when that evaluation diverges from easy outcomes. Confronting the truth takes courage, and it’s easier to make conclusions upstream of details because it spares you the emotional cost of grappling with confounding or unpalatable nuance.</blockquote>
<blockquote>Andy Grove discusses the Peter Principle, or leaders “rising to the level of their incompetence.” A common excuse for managers when promoting someone to a title they underperform in is “oh, it’s fine if they struggle, they’re learning.” Andy’s response: “It’s great that they’re learning, but remember - who’s paying their tuition? The team underneath the person who is flailing.”

I think the Peter Principle is often misread as a flippant or cynical observation rather than an objective observation, but it’s absolutely the latter. It’s only natural when promoting someone into a role or scope they’ve never had before that they’ll struggle to adapt, at least for some time.</blockquote>]]></description>
<dc:subject>management vulnerability leadership performance productmanagement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:3ab727857db9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:vulnerability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:leadership"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://archive.ph/2024.12.01-042023/https://www.washingtonpost.com/wellness/2024/11/30/discomfort-grit-womens-soccer-coaching/">
    <title>A winning mix: High standards, high support - The Washington Post</title>
    <dc:date>2025-03-14T18:03:51+00:00</dc:date>
    <link>https://archive.ph/2024.12.01-042023/https://www.washingtonpost.com/wellness/2024/11/30/discomfort-grit-womens-soccer-coaching/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>What if we could reframe our attitude and see discomfort as a sign of progress? Researchers from Cornell University and the University of Chicago instructed 557 improv students to embrace discomfort as an indicator of learning and skill development.
Students who were told to seek discomfort took more risks, persisted longer in the exercises and reported a greater sense of achievement. Comfort might be fine for keeping warm, but when we feel comfortable, “we’re often not advancing,” says Kaitlin Woolley, a marketing professor at Cornell and one of the study’s researchers.</blockquote>]]></description>
<dc:subject>psychology behavior discomfort support standards growth excellence management parenting productmanagement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:360f3074d984/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:psychology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:behavior"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:discomfort"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:support"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:growth"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:excellence"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:parenting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.figma.com/blog/welcome-to-the-wip/">
    <title>Welcome to the WIP | Figma Blog</title>
    <dc:date>2025-03-10T16:29:46+00:00</dc:date>
    <link>https://www.figma.com/blog/welcome-to-the-wip/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>a way for company leaders to indicate the importance of their feedback. It’s essentially a hashtag they put at the end of their feedback to indicate how much they care, or as the saying goes, to what degree they’re willing “to die on that hill.”

For example:

#fyi means there’s no hill to die on.
#suggestion means they’ve seen the hill but don’t feel strongly enough to commit the energy to climb it. Take it or leave it.
#recommendation means the hill was climbed. They thought about dying on it, but walked back down.
And finally, #plea means that they do, in fact, want to die on the hill. So if you see this flashtag, you better make sure it’s prioritized!</blockquote>]]></description>
<dc:subject>feedback reviews management patterns communication figma hashtags comments productmanagement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:a8015cf4b580/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:feedback"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:reviews"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:patterns"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:figma"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:hashtags"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:comments"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.leadingsapiens.com/psychological-safety-vs-high-standards/">
    <title>Psychological Safety vs. High Standards: A Misunderstood Dynamic</title>
    <dc:date>2025-02-16T04:18:19+00:00</dc:date>
    <link>https://www.leadingsapiens.com/psychological-safety-vs-high-standards/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>The term “psychological safety” is often misleading. When managers hear safety, many dismiss it as a soft style that implies complacency. Meanwhile, psychology implies too much mumbo jumbo. High-profile figures like Elon Musk advocating for a “hardcore” style perpetuate this misconception. But this is a fundamental misunderstanding of the relationship between high standards and psychological safety.

In this piece, I unpack the confusion surrounding psychological safety and why you need both psychological safety and high standards to achieve high performance.</blockquote>]]></description>
<dc:subject>psychology safety management teams culture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:359a6e790604/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:psychology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:safety"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:teams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://zuplo.com/blog/2025/01/24/api-rate-limiting">
    <title>What is API Rate Limiting? | Zuplo Blog</title>
    <dc:date>2025-01-31T05:38:08+00:00</dc:date>
    <link>https://zuplo.com/blog/2025/01/24/api-rate-limiting</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>apis ratelimiting rates management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:41a11f6b5405/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ratelimiting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:rates"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://aeon.co/ideas/why-hiring-the-best-people-produces-the-least-creative-results">
    <title>Why hiring the ‘best’ people produces the least creative results | Aeon Ideas</title>
    <dc:date>2025-01-08T04:40:08+00:00</dc:date>
    <link>https://aeon.co/ideas/why-hiring-the-best-people-produces-the-least-creative-results</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>character of complex problems also undermines the principle of meritocracy: the idea that the ‘best person’ should be hired. There is no best person. When putting together an oncological research team, a biotech company such as Gilead or Genentech would not construct a multiple-choice test and hire the top scorers, or hire people whose resumes score highest according to some performance criteria. Instead, they would seek diversity. They would build a team of people who bring diverse knowledge bases, tools and analytic skills. That team would more likely than not include mathematicians (though not logicians such as Griffeath). And the mathematicians would likely study dynamical systems and differential equations.</blockquote>]]></description>
<dc:subject>diversity creativity management dimensions thinking</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:57c16b21a3ae/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:diversity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:creativity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:dimensions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:thinking"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://landley.net/history/mirror/institutional_memory.html">
    <title>wrttn:04af1a</title>
    <dc:date>2024-12-24T08:30:14+00:00</dc:date>
    <link>https://landley.net/history/mirror/institutional_memory.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Institutional memory comes in two forms: people and documentation. People remember how things work and why. Sometimes they write it down and store that information somewhere. Institutional amnesia works similarly. The people leave and the documents disappear, rot, or just become forgotten (as it were).

I worked for several decades at a large petrochemical company. In the early 1980s, we designed and built a plant that refines some hydrocarbon type stuff into other hydrocarbon type stuff. Over the next thirty years, institutional memory of this plant faded to a dim recollection. Oh, it still operates, and still makes money for the firm. Day to day maintenance is performed, and the skilled local crew is familiar with the controls, valves, safety systems, and other such.</blockquote>]]></description>
<dc:subject>memory docs management history company documentation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:132b33d1864e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:memory"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:docs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:company"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://en.wikipedia.org/wiki/Parkinson%27s_law">
    <title>Parkinson's law - Wikipedia</title>
    <dc:date>2024-12-20T17:33:09+00:00</dc:date>
    <link>https://en.wikipedia.org/wiki/Parkinson%27s_law</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>The first-referenced meaning of the law – "Work expands to fill the available time" – has sprouted several corollaries, the best known being the Stock-Sanford corollary to Parkinson's law:

If you wait until the last minute, it only takes a minute to do.[2]

Other corollaries include Horstman's corollary to Parkinson's law, coined by Mark Horstman of website manager-tools.com:[3]

Work contracts to fit in the time we give it.</blockquote>]]></description>
<dc:subject>work laws deadlines psychology management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:140a5a36eeba/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:work"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:laws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deadlines"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:psychology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://catswetel.com/blog/2021/5/4/an-extended-subtweet-on-power">
    <title>An extended subtweet on power — Cat Swetel</title>
    <dc:date>2024-12-04T05:39:22+00:00</dc:date>
    <link>https://catswetel.com/blog/2021/5/4/an-extended-subtweet-on-power</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>the three types of power commonly discussed in management theory: power-over, power-with, and power-to. These three types of power were first identified by the Mother of Modern Management, Mary Parker Follett. You may also recognize her as the person who coined the term “win-win.” Here are the three types of power: 

Power-over is extractive. Power-over is extracted from other people, the natural world, etc. Power-over means getting more of the pie. 

Power-with is gained when we work together, i.e, collective action. Power-with means making the pie bigger as a result of all of us making pie together. 

Power-to is productive and generative. Power-to is the power we have to create new things. Power-to means making the pie bigger in some new way or even making a new and different pie. </blockquote>]]></description>
<dc:subject>power management leadership</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:1e85610b5550/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:power"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:leadership"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.catharsisinsight.com/reports">
    <title>reports | Catharsis Consulting</title>
    <dc:date>2024-11-25T04:35:39+00:00</dc:date>
    <link>https://www.catharsisinsight.com/reports</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Themes from these interviews revealed an important learning tension: the work that code writers needed to do to understand code often did not feel like what was rewarded in the evaluation of their work. Code review often did not recognize code writers’ effort when it did not result in lines of code. Despite stated ideals about knowledge sharing (e.g., documentation and collaboration), this work was often contradicted with negative cues from colleagues about what was “truly” valued. This tension was exacerbated by code writers’ fears about “not looking like an engineer,” and their desire to perform to the expectations of their environments.

 

Code writers navigated this by divesting from their own learning and from the “invisible” work of knowledge transfer, leaving future collaborators without guidance in their own ramp-up to unfamiliar code. As a result, code writers frequently expressed a poignant loneliness, even in highly resourced teams. This maladaptive cycle can be understood as Learning Debt. Research from learning science describes how environments that discourage sharing mistakes and valuing “in-draft” effort lead to long-term costs in people’s motivation, wellbeing, and learning. Under this discouragement, even formal processes which are ostensibly meant to maintain productivity and provide support (e.g., code review, conversations with senior code authors) can reinforce these negative norms</blockquote>]]></description>
<dc:subject>management programming learning culture incentives</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:ef8f5cf01019/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:learning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:incentives"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://psychsafety.co.uk/the-seven-deadly-sins-of-psychological-safety/">
    <title>The Seven Deadly Sins of Psychological Safety - Psych Safety</title>
    <dc:date>2024-11-25T03:41:38+00:00</dc:date>
    <link>https://psychsafety.co.uk/the-seven-deadly-sins-of-psychological-safety/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>“That’s a terrible idea.”
“You should know that by now.”
“Whose fault is this?”
“Everyone is replaceable.”
“Don’t bring me problems, bring me solutions.”
“Just get it done.”
“Not now, I’m too busy.”</blockquote>]]></description>
<dc:subject>safety psychological culture management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:6f0277220b7a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:safety"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:psychological"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://waysofworkingcollection.substack.com/p/okrs-arent-the-only-way-how-to-identify?triedRedirect=true">
    <title>OKRs aren't the only way. How to identify the right types of goals for your team.</title>
    <dc:date>2024-09-24T05:14:04+00:00</dc:date>
    <link>https://waysofworkingcollection.substack.com/p/okrs-arent-the-only-way-how-to-identify?triedRedirect=true</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>not enough time on deciding if the type of goals they have chosen are the right ones in the first place.

What are the different types of goals?
Below I’ve identified 5 types of goals, which fall into 3 categories:

Doing something new: Discovery and Zero-to-One type goals.

Building on the existing: Iterate and Scale type goals.

Business as usual: The day-to-day work that is often overlooked and not classified as goals, but requires your team's bandwidth</blockquote>]]></description>
<dc:subject>okrs goals management productmanagement criticism</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:7a5efd2cb36c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:okrs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:goals"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:criticism"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://skamille.medium.com/founders-create-managers-aba3c88981ba">
    <title>Founders Create Managers. There’s a new pg article making the… | by Camille Fournier | Sep, 2024 | Medium</title>
    <dc:date>2024-09-03T06:10:12+00:00</dc:date>
    <link>https://skamille.medium.com/founders-create-managers-aba3c88981ba</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>My assertion is that “founder mode”, naively applied, creates the very conditions that lead to those nefarious professional managers. I’ve seen it happen at companies big and small with founder-type leaders. The process goes something like this:</blockquote>]]></description>
<dc:subject>management founders scaling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:d2395e5f3314/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:founders"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:scaling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.forrester.com/blogs/boomi-dismembers-the-tibco-frankenstein/">
    <title>Boomi Dismembers The TIBCO Frankenstein Through Acquisitions</title>
    <dc:date>2024-07-19T05:58:26+00:00</dc:date>
    <link>https://www.forrester.com/blogs/boomi-dismembers-the-tibco-frankenstein/</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>tibco apis management vendors</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:d6ace4965bd0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tibco"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:vendors"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.youtube.com/watch?v=P4VBqTViEx4">
    <title>Designer's Digest - Steve Jobs on the role of product and marketing people. - YouTube</title>
    <dc:date>2024-05-02T20:59:11+00:00</dc:date>
    <link>https://www.youtube.com/watch?v=P4VBqTViEx4</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[a version of enshittification
tonerheads or copierheads]]></description>
<dc:subject>business management videos steve_jobs xerox</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:138e37e24a5a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:videos"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:steve_jobs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:xerox"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/@jurgenappelo/the-7-levels-of-delegation-672ec2a48103">
    <title>The 7 Levels of Delegation. Empowerment with Boundaries and Clarity | by Jurgen Appelo | Medium</title>
    <dc:date>2024-04-10T01:47:59+00:00</dc:date>
    <link>https://medium.com/@jurgenappelo/the-7-levels-of-delegation-672ec2a48103</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>That’s why a person wanting to delegate work to someone else can benefit from the use of the seven levels of delegation.

1. Tell: You make a decision for others and you may explain your motivation. A discussion about it is neither desired nor assumed.

2. Sell: You make a decision for others but try to convince them that you made the right choice, and you help them feel involved.

3. Consult: You ask for input first, which you take it into consideration before making a decision that respects people’s opinions.

4. Agree: You enter into a discussion with everyone involved, and as a group you reach consensus about the decision.

5. Advise: You will offer others your opinion and hope they listen to your wise words, but it will be their decision, not yours.

6. Inquire: You first leave it to the others to decide, and afterwards, you ask them to convince you of the wisdom of their decision.

7. Delegate: You leave the decision to them and you don’t even want to know about details that would just clutter your brain.</blockquote>]]></description>
<dc:subject>decisions framework leadership management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:c85592838ba8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:decisions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:framework"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:leadership"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.appliedcomputing.io/p/okrs-are-bullshit">
    <title>OKRs are Bullshit - by drmorr</title>
    <dc:date>2024-04-06T14:39:21+00:00</dc:date>
    <link>https://blog.appliedcomputing.io/p/okrs-are-bullshit</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>the biggest problem with OKR's laser focus on measurement, though, is that not everything should be measured, even if you can! Being "data-driven" is a huge buzzword in the industry. We want to improve, we want to see how much we improved by, and then we want to tell the world how much we improved by so our stock price goes up.</blockquote>]]></description>
<dc:subject>metrics business management process planning okrs criticism</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:ae16fbb4ef10/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:metrics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:process"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:planning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:okrs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:criticism"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.rawsignal.ca/">
    <title>Raw Signal Group</title>
    <dc:date>2024-03-16T20:59:50+00:00</dc:date>
    <link>https://www.rawsignal.ca/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Management and leadership training for leaders in growing organizations. No trust falls. No personality tests. Just the concrete skills you need to do hard things.</blockquote>]]></description>
<dc:subject>management training leadership</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:e0b359f17ff2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:training"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:leadership"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://noidea.dog/glue">
    <title>Being Glue — No Idea Blog</title>
    <dc:date>2024-03-02T19:37:53+00:00</dc:date>
    <link>https://noidea.dog/glue</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>career leadership management glue</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:7d391317f6bd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:career"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:leadership"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:glue"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://randsinrepose.com/archives/shields-down/">
    <title>Shields Down – Rands in Repose</title>
    <dc:date>2024-02-22T21:26:09+00:00</dc:date>
    <link>https://randsinrepose.com/archives/shields-down/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Your shields drop the moment you let a glimpse of a potential different future into your mind. It seems like a unconsidered off-the-cuff thought sans consequence, but the thought opens you to possibilities that did not exist the moment before the thought existed.

What is incredibly slippery about this moment is the complex, nuanced, and instant mental math performed that precedes the shields-down situation. When you are indirectly asked to lower your shields, you immediately parse, place a value, and aggregate your opinions on the following:

Am I happy with my job?
Do I like my manager? My team?
Is this project I’m working on fulfilling?
Am I learning?
Am I respected?
Am I growing?
Do I feel fairly compensated?
Is this company/team going anywhere?
Do I believe in the vision?
Do I trust the leaders?</blockquote>]]></description>
<dc:subject>career management culture jobs switching leadership</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:193adb58541f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:career"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:jobs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:switching"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:leadership"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://intenseminimalism.com/2015/a-framework-for-thinking-about-systems-change/">
    <title>A Framework for Thinking About Systems Change · Intense Minimalism</title>
    <dc:date>2024-01-27T06:34:16+00:00</dc:date>
    <link>https://intenseminimalism.com/2015/a-framework-for-thinking-about-systems-change/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Confusion → lack of Vision: note that this can be a proper lack of vision, or the lack of understanding of that vision, often due to poor communication and syncrhonization of the people involved.
Anxiety → lack of Skills: this means that the people involved need to have the ability to do the transformation itself and even more importantly to be skilled enough to thrive once the transformation is completed.
Resistance → lack of Incentives: incentives are important as people tend to have a big inertia to change, not just for fear generated by the unknown, but also because changing takes energy and as such there needs to be a way to offset that effort.
Frustration → lack of Resources: sometimes change requires very little in terms of practical resources, but a lot in terms of time of the individuals involved (i.e. to learn a new way to do things), lacking resources will make progress very slow and it’s very frustrating to see that everything is aligned and ready, but doesn’t progress.
False Starts → lack of Action Plan: action plans don’t have to be too complicated, as small transformative changes can be done with little structure, yet, structure has to be there. For example it’s very useful to have one person to lead the charge, and everyone else agreeing they are the right person to make things happen.</blockquote>]]></description>
<dc:subject>change frameworks leadership management systems</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:b469814c24aa/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:change"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:frameworks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:leadership"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:systems"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://faculty.haas.berkeley.edu/mhsu/blog/files/deming_measurement.html">
    <title>So you CAN manage what you can't measure? | Marketing Research, Science of Business</title>
    <dc:date>2024-01-21T07:19:21+00:00</dc:date>
    <link>https://faculty.haas.berkeley.edu/mhsu/blog/files/deming_measurement.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Little did I know that in fact: (i) Drucker didn't say it, (ii) Deming didn't say it, (iii) Deming said something similar, but meant something completely the opposite.

The actual quote, by Deming, is, "It is wrong to suppose that if you can’t measure it, you can't manage it—a costly myth".</blockquote>]]></description>
<dc:subject>quotes measurement management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:25cde3685f54/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:quotes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:measurement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://jacobian.org/2023/dec/1/against-rfcs/">
    <title>RFC processes are a poor fit for most organizations - Jacob Kaplan-Moss</title>
    <dc:date>2023-12-03T02:15:30+00:00</dc:date>
    <link>https://jacobian.org/2023/dec/1/against-rfcs/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>The IETF’s RFC home page holds a key hint to why they tend to work poorly outside of standards bodies:

Software developers, hardware manufacturers, and network operators around the world voluntarily implement and adopt the technical specifications described by RFCs.

Did you catch the problem? It’s these two words: “voluntarily implement.”

Why RFCs fail in corporate settings
The crux of the problem with RFC processes in corporate settings is that the process, as designed, doesn’t include any sort of decision-making framework. They are, as the person whose quote opened this piece described, a “document and discuss” framework – and not a decision-making framework. RFCs are written and discussed, but there’s no mechanism by which they’re formally adopted or rejected. Organizations choose to implement them (or don’t); they become standards through widespread voluntary adoption.</blockquote>]]></description>
<dc:subject>decisions management rfcs work culture standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:1bb530ee7c38/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:decisions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:rfcs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:work"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://staysaasy.com/startups/2023/11/10/imprecise-asks.html">
    <title>Your Small Imprecise Ask Is a Big Waste of Their Time | Stay SaaSy</title>
    <dc:date>2023-11-27T18:24:46+00:00</dc:date>
    <link>https://staysaasy.com/startups/2023/11/10/imprecise-asks.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Do not, DO NOT, assume they are too busy to answer clarifying questions as you work on the ask. Dollars are flushed down the drain every day because people incorrectly assume leaders don’t have time to clarify their asks. Rooms full of people analyze emails and instant messages from the leader like ancient artifacts. Ask the leader for clarification - if they have time to ask you to do something, they have time to clarify that ask.</blockquote>]]></description>
<dc:subject>leadership management productmanagement costs</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:51981572b399/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:leadership"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:costs"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://hbr.org/2007/11/a-leaders-framework-for-decision-making">
    <title>A Leader’s Framework for Decision Making</title>
    <dc:date>2023-10-25T04:13:02+00:00</dc:date>
    <link>https://hbr.org/2007/11/a-leaders-framework-for-decision-making</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Archive: https://archive.ph/20250326095244/https://hbr.org/2007/11/a-leaders-framework-for-decision-making#0
<blockquote>
The term "Cynefin" (pronounced ku-nev-in) is a Welsh word that roughly translates to "habitat" or "place." It was popularized by Dave Snowden as a framework to help decision-makers understand the complexity of different types of problems and situations. The term was chosen to evoke a sense of the complexities around the different environments in which decisions are made. It categorizes problems into five domains: Simple (or Clear), Complicated, Complex, Chaotic, and Aporetic (or Confused).

Think of Cynefin as a map: just as a topographical map helps you understand landscapes, the Cynefin framework helps you navigate the terrain of decision-making by showing you the nature of the problem at hand.

Cynefin doesn't offer solutions but provides a way to understand the context so that you can apply appropriate problem-solving methods.
</blockquote>]]></description>
<dc:subject>complexity leadership management frameworks productmanagement decisions</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:07e359b4a26c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:complexity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:leadership"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:frameworks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:decisions"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://everythingchanges.us/blog/energy-makes-time/">
    <title>Energy makes time | everything changes</title>
    <dc:date>2023-09-14T00:16:15+00:00</dc:date>
    <link>https://everythingchanges.us/blog/energy-makes-time/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Then one day they say fuck it all. They eat leftover pasta over the sink, drop mom off at her mahjongg game, and go sit in the park to draw. They draw for hours, until the sun goes down and they’re squinting under the street lights. And, lo and behold, the next day they plow through all those lingering to-dos. They see clearly that half of them were unnecessary when before they all seemed critical. They recognize a few others as things better handed off to their peers. They suddenly find time for attending to that one project they’d been procrastinating on for weeks. They sleep better. Their skin looks great. (Okay I might be exaggerating on that last one, but only mildly.)

It turns out, not doing their art was costing them time, was draining it away, little by little, like a slow but steady leak. They had assumed, wrongly, that there wasn’t enough time in the day to do their art, because they assumed (because we’re conditioned to assume) that every thing we do costs time. But that math doesn’t take energy into account, doesn’t grok that doing things that energize you gives you time back. By doing their art, a whole lot of time suddenly returned. Their art didn’t need more time; their time needed their art.</blockquote>]]></description>
<dc:subject>creativity productivity time energy management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:a0962f2a0d2f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:creativity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productivity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:time"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:energy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://knowyourteam.com/blog/2019/10/03/skip-level-meetings-what-they-are-and-exactly-how-to-run-them/">
    <title>Skip-level meetings: What they are, and exactly how to run them - Know Your Team | Blog</title>
    <dc:date>2023-09-06T00:14:32+00:00</dc:date>
    <link>https://knowyourteam.com/blog/2019/10/03/skip-level-meetings-what-they-are-and-exactly-how-to-run-them/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Before your skip-level meeting, take 15 minutes to do the two following things:

#1: Get up-to-speed.
Your skip-level meeting should not be spent getting caught up on the employee’s latest project. You can read about that in Slack, Basecamp, Trello, etc. So any time you spend asking “What’s the latest on X?” you’ve wasted invaluable time in your skip-level meeting. Instead, review status updates ahead of time.

#2: Co-create an agenda.
Spend time brainstorming 5–7 questions that you want to ask the employee — and then send the agenda over to the employee to get their input and have them add any questions they’d like.

On your end, at least one of the agenda questions should be something that helps establish trust or rapport in the beginning, to help your employees feel more comfortable before diving into the conversation. The rest of the questions should be focused on either feedback, issues/concerns in the company, and/or career direction. Lastly, you’ll then want to leave 10 or so minutes at the end of the agenda to discuss the next steps and takeaways.

Here’s an example of a skip-level meeting agenda:

Personal connection (10 minutes) Concerns/Issues (20 minutes)

As a company, do you think we’re behind the curve on anything in particular?
When have you been disappointed with a decision or the direction that the company has gone in the past quarter?
What rumors are you hearing that you think I should know about?
Feedback (20 minutes)

When have you felt most proud of being a part of the company this past year?
Could I be doing a better job outlining the vision and direction for where we’re headed?
Takeaways / next steps (10 minutes)</blockquote>]]></description>
<dc:subject>management skip meetings preparation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:63dcdbd8cc39/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:skip"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:meetings"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:preparation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://news.ycombinator.com/item?id=25855303">
    <title>One of my all time favorites. Can’t remember where I first read it (Quora?), but... | Hacker News</title>
    <dc:date>2023-06-15T16:29:10+00:00</dc:date>
    <link>https://news.ycombinator.com/item?id=25855303</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[A man is flying in a hot air balloon and realizes he is lost. He reduces height and spots a man down below. He lowers the balloon further and shouts:

"Excuse me, can you help me? I promised my friend. I would meet him half an hour ago, but I don't know where I am."

The man below says, "Yes, you are in a hot air balloon, hovering approximately 30 feet above this field. You are between 40 and 42 degrees North latitude, and between 58 and 60 degrees West longitude."

"You must be a programmer," says the balloonist.

"I am," replies the man. "How did you know?"

"Well," says the balloonist, "everything you have told me is technically correct, but I have no idea what to make of your information, and the fact is I am still lost."

The man below says, "You must be a project manager"

"I am," replies the balloonist, "but how did you know?"

"Well," says the man, "you don't know where you are or where you are going. You have made a promise which you have no idea how to keep, and you expect me to solve your problem. The fact is you are in the exact same position you were in before we met, but now it is somehow my fault."]]></description>
<dc:subject>jokes programming development engineers projects management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:4ce0b6d3e677/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:jokes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:engineers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:projects"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://joshmcla.medium.com/manage-stakeholders-more-effectively-with-aai-not-raci-7982c79c8ba6">
    <title>Manage stakeholders more effectively with AAI, not RACI | by Joshua McLaughlin | Medium</title>
    <dc:date>2023-05-08T06:18:38+00:00</dc:date>
    <link>https://joshmcla.medium.com/manage-stakeholders-more-effectively-with-aai-not-raci-7982c79c8ba6</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Key components of the AAI framework
The three components of Awareness, Alignment, and Inclusion that make up the AAI framework are defined as:

Awareness: This refers to anyone who is impacted by, or has the ability to affect the outcome of a task or decision, even if they don’t have direct authority.
Alignment: This refers to who has the power to make decisions and take action on a task.
Inclusion: This refers to who is responsible for executing a task or making a decision.
</blockquote>]]></description>
<dc:subject>projectmanagement project management farmeworks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:41eb3607bcf0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:projectmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:project"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:farmeworks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://chrisgagne.com/1255/mary-poppendiecks-the-tyranny-of-the-plan/">
    <title>Mary Poppendieck’s “The Tyranny of ‘The Plan’” – Chris Gagné</title>
    <dc:date>2023-02-09T01:12:06+00:00</dc:date>
    <link>https://chrisgagne.com/1255/mary-poppendiecks-the-tyranny-of-the-plan/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[On the empire state building and the miracle of building it as a project plan.
<blockquote>So when we have this thing called variance from plan against which basically most project managers happen to be measured from their basic performance, right? Okay, how are we doing with earned value and that sort of thing. Basic project management measurement is variance from plan. So say you vary from plan. What happens? Oh, you’ve got a performance failure, right? Maybe. There is another way to look at performance from schedule. Perhaps it’s not the person who’s trying to manage the schedules fault. Perhaps it’s the schedule’s fault instead. In fact, if the schedule is a hypothesis rolled up from a lot of detail, it’s the schedule’s fault, not the person’s fault and what we really should do is view it as a learning opportunity.</blockquote>
<blockquote>
There’s one thing that’s missing that you see in every entrepreneurial company starting up and it’s called “that entrepreneur,” the guy with the big idea that understands the technology and understands the customers. What we don’t have in corporate IT is any concept that even comes close to a product manager or anything like that that you find in every product company. Somebody that has a vision of what the customers really want and what the technology is capable of and can make those tradeoffs. Instead, too much of the IT people are order takers. Go to the business and do whatever they say. That’s not the concept. The concept is to understand well enough what’s needed out there to make aggressive tradeoffs so that you can figure out how to design to fit the constraints. That means there’s got to be somebody there that can make those choices and say “no, we don’t need that. That can be later.” Typically IT departments lack that, but companies that are trying to start new products have only so much money. They’re much more capable of making those tradeoff decisions and you need somebody that’s in a position to make the “yes, we’ve got to have this, no we can do without that,” decisions and they’re tough decisions. There is typically is no role in IT departments to make those tradeoffs.
</blockquote>]]></description>
<dc:subject>management planning projectmanagement lean empire</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:3600e99d6b22/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:planning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:projectmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:lean"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:empire"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/smells-like-team-spirit/should-management-be-on-your-career-path-a6aa6b7aad0a">
    <title>Should management be on your career path? | by Sean Regan | Smells Like Team Spirit | Medium</title>
    <dc:date>2023-01-28T01:28:30+00:00</dc:date>
    <link>https://medium.com/smells-like-team-spirit/should-management-be-on-your-career-path-a6aa6b7aad0a</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>from the former head of product marketing at Atlassian to everyone within his team. But it's also great advice, when flipped, for managers. For example, the first point: "1: Managing your career path is your responsibility" - is true for the manager as well. "Managing your reports' career paths is your responsibility, too." Or "9: Get comfortable with being uncomfortable" flipped is "Make it safe for the people on your team to be uncomfortable."</blockquote>]]></description>
<dc:subject>management career responsibility advice</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:ea2b664e415f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:career"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:responsibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:advice"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://swiber.dev/future-of-api-management-in-2023-and-beyond">
    <title>🔮 Future of API Management in 2023 and Beyond | Learn APIs with Kevin</title>
    <dc:date>2023-01-12T02:17:46+00:00</dc:date>
    <link>https://swiber.dev/future-of-api-management-in-2023-and-beyond</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Even as some components of API Management platforms head toward commodity, we'll continue to see innovations move from their genesis into the product space and into open source projects.

In 2023 and beyond, API Management platforms will:

Include more than just the runtime
Focus on key experiences
Measure what matters to all stakeholders
Allow a mix-and-match of plug-and-play components
Integrate ML/AI capabilities</blockquote>]]></description>
<dc:subject>apis management predictions</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:40451928d70b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:predictions"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.pragmaticengineer.com/project-management-at-big-tech/">
    <title>How Big Tech Runs Tech Projects and the Curious Absence of Scrum - The Pragmatic Engineer</title>
    <dc:date>2022-11-08T19:14:59+00:00</dc:date>
    <link>https://blog.pragmaticengineer.com/project-management-at-big-tech/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Autonomy for software engineers and teams. The expectation of developers at traditional companies is to complete assigned work. At SV-like companies, it's to solve problems that the business has. This is a huge difference. It impacts the day-to-day life of any engineer.
Curious problem solvers, not mindless resources. A motivated engineer easily makes multiple times the impact of a "factory worker" who only does what they’re told.  For organizations with a factory worker attitude, this approach will bias towards more heavyweight project management approaches that leave little room for interpretation, on purpose.
Internal data, code, and documentation transparency</blockquote>]]></description>
<dc:subject>process management scrum agile programming comparison</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:467711a58bfa/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:process"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:scrum"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:comparison"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://skamille.medium.com/opp-other-peoples-problems-d7eb174724ee">
    <title>OPP (Other People’s Problems). A hard lesson for me over the past… | by Camille Fournier | Medium</title>
    <dc:date>2022-11-04T16:36:25+00:00</dc:date>
    <link>https://skamille.medium.com/opp-other-peoples-problems-d7eb174724ee</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>OPP (Other People’s Problems)
A hard lesson for me over the past several years of my career has been figuring out how to pick my battles. I’ve seen many friends and colleagues struggle with this as well: how do you know when to involve yourself in something, and how do you know when to stay out of it? How do you figure out where the line is?</blockquote>]]></description>
<dc:subject>culture management people problems productmanagement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:cd4649e04b8b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:people"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:problems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.industriallogic.com/blog/scatter-gather/">
    <title>Scatter-Gather</title>
    <dc:date>2022-10-20T02:35:33+00:00</dc:date>
    <link>https://www.industriallogic.com/blog/scatter-gather/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>There is a prevalent way of managing people in a software process that involves a fair amount of work to ensure that each person gets tasks that are appropriate to their talent, knowledge, skill, and experience.

For a given feature or modification to a software product, a senior technical person will work out a design that is likely to be successful and fit into the business architecture. This master-maker will then divide the work into tasks that need to be completed by individuals.

Often a good master technician will consider their team’s skills and divide the work along individual skill lines. Some will divide the work along component lines and then consider which team member will be given which part to work on based on the components they know best.

The work is assigned and then the team members perform the new work when they complete their current task list, asking questions of the senior person as needed, and hopefully (in many but not all organizations) will test their pieces independently.</blockquote>]]></description>
<dc:subject>leadership agile management processes software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:6245f1a9027c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:leadership"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:processes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.svpg.com/coaching-tools-the-assessment/">
    <title>Coaching Tools - The Assessment - Silicon Valley Product Group : Silicon Valley Product Group</title>
    <dc:date>2022-09-16T16:54:11+00:00</dc:date>
    <link>https://www.svpg.com/coaching-tools-the-assessment/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Your cross-functional product teams depend on competent product managers, and if you don’t develop your people and provide growth opportunities, there are usually other companies that will.  I have always been a big believer in the old adage that “people join a company, but leave their manager.”

This article discusses the technique that I use and advocate for assessing a product manager. It is the foundation for then coaching the person to success.

This skills assessment is structured in the form of a gap analysis.  The purpose is to assess the product manager’s current level of competence along each of several necessary dimensions, and then compare that with the level of competence that’s required for this particular team and company.

This format acknowledges that not all skills are equally important, not all gaps are equally significant, and expectations change with the level of responsibility.  This tool is intended to help focus the attention where it is most needed.</blockquote>]]></description>
<dc:subject>productmanagement management coaching product assessment framework</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:e7c3340e5cc3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:coaching"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:product"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:assessment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:framework"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://apenwarr.ca/log/20201227">
    <title>Systems design explains the world: volume 1 - apenwarr</title>
    <dc:date>2022-08-31T23:17:24+00:00</dc:date>
    <link>https://apenwarr.ca/log/20201227</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>The trick is to determine whether you actually have one of these exact "disruption" things. They're rare. And as an early startup, you don't yet have a historical plot like the one above that makes it clear; you have to convince yourself that you'll realistically be able to improve your thing faster than the incumbent can improve theirs, over a long period of time.

Or, if your innovation only depends on an existing trend - like in the software-based packet processing example above - then you can try to time it so that your software product is ready to mature at the same time as the hardware trend crosses over.</blockquote>]]></description>
<dc:subject>systems thinking culture innovation dilemma architecture design management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:60865ad11038/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:systems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:thinking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:innovation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:dilemma"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://cutlefish.substack.com/p/20-things-ive-learned-as-a-systems?s=r">
    <title>20 Things I've Learned as a Systems (Over) Thinker</title>
    <dc:date>2022-08-23T05:37:58+00:00</dc:date>
    <link>https://cutlefish.substack.com/p/20-things-ive-learned-as-a-systems?s=r</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Take care of yourself. Your brain is working overtime—all the time. Practice “radical” recovery.

You may spend a lot longer thinking about things than most people. Pace your delivery.

If you go deep first, and then simplify…keep in mind that you don’t need to show all of your work.

Your default description of (almost) any problem will be too threatening/overwhelming.

Do your deepest thinking with co-conspirators (not the people you’re trying to influence).

Informal influence is often not formally recognized. Prepare mentally for this.

The people you’re trying to influence spend 98% of their day overwhelmed by business as usual.

Remember to also do the job you were hired to do (if you don’t you’ll be easier to discount).

Seek “quick wins”, but know that most meaningful things will take a while.

Some things take ages to materialize. It is discontinuous, not continuous.

Make sure to celebrate your wins. They will be few and far between, so savor the moment.

The people who support you in private may not be able to support you in public. Accept that.

Hack existing power structures—it’s much easier than trying to change them.

Consider becoming a formal leader. It’s harder in many ways, but you’ll have more leverage. What’s stopping you?

In lieu of being a formal leader, make sure to partner with people who actually “own” the area of change.

Watch out for imposing your worldview on people. Have you asked about what people care about?.

You’ll need a support network. And not just a venting network. Real support.

“Know when to fold ‘em”. Listen to Kenny Rogers The Gambler. Leave on your own terms.

Don’t confuse being able to sense/see system dynamics, with being about to “control” them. You can’t.

Grapple with your demons, and make sure not to wrap up too much of your identity in change</blockquote>]]></description>
<dc:subject>management systems productmanagement thinker</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:d12e3f6edde3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:systems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:thinker"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://dscout.com/people-nerds/organizational-trauma">
    <title>dscout + HmntyCntrd: Challenging Company Playbooks to Workplace Trauma</title>
    <dc:date>2022-08-23T05:04:58+00:00</dc:date>
    <link>https://dscout.com/people-nerds/organizational-trauma</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>business productivity psychology work management covid trauma culture responses</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:1f389423dc64/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productivity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:psychology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:work"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:covid"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:trauma"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:responses"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://cdn.ymaws.com/www.tocico.org/resource/resmgr/2012_conf_pdfs/goldratt,_rami_management_at.pdf">
    <title>2012 International Conference Videos Goldratt, Rami - Management Attention - Achieving results dealing with complexity, uncertainty and conflicts</title>
    <dc:date>2022-05-31T15:47:10+00:00</dc:date>
    <link>https://cdn.ymaws.com/www.tocico.org/resource/resmgr/2012_conf_pdfs/goldratt,_rami_management_at.pdf</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Goldratt: 
The real constraint: Management Attention.
 The 3 fundamental mechanisms wasting and
distorting management attention:
 The fear of Complexity -> driving to dissect the system to
sub-systems and bringing damaging local optima.
 The fear of Unknown-> driving to manage by finer and
finer detail resolution, optimizing within the noise.
 The fear of tug of war -> struggling with
unacceptable compromises. 

see video: https://www.tocico.org/page/12ConfVid17]]></description>
<dc:subject>management attention conflicts organization culture slides</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:abcf2e350705/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:attention"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:conflicts"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:organization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:slides"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://hbr.org/2020/11/how-apple-is-organized-for-innovation">
    <title>How Apple Is Organized for Innovation</title>
    <dc:date>2022-04-20T15:29:08+00:00</dc:date>
    <link>https://hbr.org/2020/11/how-apple-is-organized-for-innovation</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[a competitive advantage]]></description>
<dc:subject>management innovation apple productmanagement culture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:d197dfe0b9d2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:innovation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apple"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.idevnews.com/stories/7509/API-Management-vs-Service-Mesh-The-Choice-Doesnt-Have-to-Be-Yours">
    <title>Idevnews | API Management vs. Service Mesh: The Choice Doesn’t Have to Be Yours</title>
    <dc:date>2022-04-16T15:22:41+00:00</dc:date>
    <link>https://www.idevnews.com/stories/7509/API-Management-vs-Service-Mesh-The-Choice-Doesnt-Have-to-Be-Yours</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[""]]></description>
<dc:subject>apis services mesh comparison management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:eb3f4a79d702/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:services"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:mesh"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:comparison"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://forcemultipliers.substack.com/p/setting-up-your-new-pm-hire-to-win?s=r">
    <title>Onboarding a new PM - by Umang Jaipuria</title>
    <dc:date>2022-04-11T16:04:42+00:00</dc:date>
    <link>https://forcemultipliers.substack.com/p/setting-up-your-new-pm-hire-to-win?s=r</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["For Product Managers, onboarding should have two goals:

Prove they are worthy

For leadership roles, particularly product management that leans heavily on the amorphous form of power that is influence, this is by far the most important thing in the early days. It is why nearly every piece of PM advice for ramping up in a new job highlights the need to get an early win. All eyes are on you and winning the confidence of a broad, multi-functional group of people determines your ability to lead and hence to execute. It is not only about having a product or business win, but also about getting a handle on the decision-making and execution machinery. Which brings me to the second goal.

Build situational awareness
Product management is often considered a “glue” role, existing in the empty spaces in between other functions bringing them together. To make or facilitate decisions in a high-dimensional information space, to play moderator for conversations among people that don’t often come together requires an understanding of both the product context and organization dynamics. Whether a new PM is seen to get a handle on delicate situations, understand motivations of people and teams around them, pick up the parlance and navigate various conversations plays a critical role in building confidence with their team.

Inferring the complex and subterranean map of the product and the organization usually only happens through osmosis and you, as their manager, need to accelerate that. Components of my own playbook (relevant to a growth-stage company) are:

A State of the Union

A Mind-Meld

An Early Win"]]></description>
<dc:subject>productmanagement management onboarding process</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:dc4e92521aab/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:onboarding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:process"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://qaspire.com/2022/01/10/conversations-that-build-psychological-safety/">
    <title>Conversations That Build Psychological Safety | QAspire</title>
    <dc:date>2022-03-11T02:14:31+00:00</dc:date>
    <link>https://qaspire.com/2022/01/10/conversations-that-build-psychological-safety/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Growth in today’s world is driven by how talented people bring their best ideas on the table, work with each other in a conducive environment and choose to deliver their best effort in order to achieve the desired outcome. Companies often do great at recruiting the most talented people but fail at providing them a […]</blockquote>]]></description>
<dc:subject>management leadership safety trust tanmay_vora amy_edmondson communication via:mreinbold teams</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:8c0ff6863d6a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:leadership"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:safety"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:trust"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tanmay_vora"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:amy_edmondson"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:via:mreinbold"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:teams"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://danluu.com/people-matter/">
    <title>Individuals matter</title>
    <dc:date>2021-11-19T03:05:10+00:00</dc:date>
    <link>https://danluu.com/people-matter/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Argues that too many leaders, from HR high-ups to charity executives, treat their organizations as “SimCity” games, with a set of knobs and dials that will change things in predictable, legible, and uniform ways. Rather, individuals are non-fungible and outcomes are unevenly-distributed, and failing to realize this can lead to organizational turmoil.]]></description>
<dc:subject>people complexity management gale work fungible headcount compensation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:33fff9969673/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:people"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:complexity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:gale"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:work"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:fungible"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:headcount"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:compensation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://basecamp.com/shapeup/webbook">
    <title>Shape Up: Stop Running in Circles and Ship Work that Matters</title>
    <dc:date>2021-08-13T18:32:08+00:00</dc:date>
    <link>https://basecamp.com/shapeup/webbook</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[from basecamp folks]]></description>
<dc:subject>software development books management culture teams velocity productmanagement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:69691b31c853/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:books"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:teams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:velocity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/athensresearch/athens">
    <title>GitHub - athensresearch/athens: Free self-hosted desktop app: https://github.com/athensresearch/athens/releases; Paid tiers available through https://opencollective.com/athens; Try the demo at https://athensresearch.github.io/athens; Docs viewable at http</title>
    <dc:date>2021-07-28T01:59:50+00:00</dc:date>
    <link>https://github.com/athensresearch/athens</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["Athens is a knowledge graph for research and notetaking. Athens is open-source, private, extensible, and community-driven."

A bit like Roam but OSS]]></description>
<dc:subject>opensource knowledge graph management notes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:f130c2577fcf/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:knowledge"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:graph"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:notes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.youtube.com/watch?v=YyXRYgjQXX0">
    <title>Are you a giver or a taker? | Adam Grant - YouTube</title>
    <dc:date>2021-07-02T21:52:11+00:00</dc:date>
    <link>https://www.youtube.com/watch?v=YyXRYgjQXX0</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[""]]></description>
<dc:subject>psychology management advice culture givers takers ted videos collaboration helping</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:4294da9da108/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:psychology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:advice"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:givers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:takers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ted"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:videos"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:helping"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://skamille.medium.com/an-incomplete-list-of-skills-senior-engineers-need-beyond-coding-8ed4a521b29f">
    <title>An incomplete list of skills senior engineers need, beyond coding | by Camille Fournier | Jun, 2021 | Medium</title>
    <dc:date>2021-06-18T21:09:41+00:00</dc:date>
    <link>https://skamille.medium.com/an-incomplete-list-of-skills-senior-engineers-need-beyond-coding-8ed4a521b29f</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Not just engineers!

"How to run a meeting, and no, being the person who talks the most in the meeting is not the same thing as running it
How to write a design doc, take feedback, and drive it to resolution, in a reasonable period of time
How to mentor an early-career teammate, a mid-career engineer, a new manager who needs technical advice
How to indulge a senior manager who wants to talk about technical stuff that they don’t really understand, without rolling your eyes or making them feel stupid
How to explain a technical concept behind closed doors to a senior person too embarrassed to openly admit that they don’t understand it
How to influence another team to use your solution instead of writing their own
How to get another engineer to do something for you by asking for help in a way that makes them feel appreciated
How to lead a project even though you don’t manage any of the people working on the project
How to get other engineers to listen to your ideas without making them feel threatened
How to listen to other engineers’ ideas without feeling threatened
How to give up your baby, that project that you built into something great, so you can do something else
How to teach another engineer to care about that thing you really care about (operations, correctness, testing, code quality, performance, simplicity, etc)
How to communicate project status to stakeholders
How to convince management that they need to invest in a non-trivial technical project
How to build software while delivering incremental value in the process
How to craft a project proposal, socialize it, and get buy-in to execute it
How to repeat yourself enough that people start to listen
How to pick your battles
How to help someone get promoted
How to get information about what’s really happening (how to gossip, how to network)
How to find interesting work on your own, instead of waiting for someone to bring it to you
How to tell someone they’re wrong without making them feel ashamed
How to take negative feedback gracefully"]]></description>
<dc:subject>management programming engineering career skills productmanagement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:a833506c0a6e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:engineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:career"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:skills"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://jamesclear.com/marginal-gains">
    <title>Marginal Gains: This Coach Improved Every Tiny Thing by 1 Percent</title>
    <dc:date>2021-06-18T15:36:09+00:00</dc:date>
    <link>https://jamesclear.com/marginal-gains</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Brailsford had been hired to put British Cycling on a new trajectory. What made him different from previous coaches was his relentless commitment to a strategy that he referred to as “the aggregation of marginal gains,” which was the philosophy of searching for a tiny margin of improvement in everything you do. Brailsford said, “The whole principle came from the idea that if you broke down everything you could think of that goes into riding a bike, and then improve it by 1 percent, you will get a significant increase when you put them all together.”]]></description>
<dc:subject>productivity coaching cycling management improvements betterment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:e7f73cd4f6d3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productivity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:coaching"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:cycling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:improvements"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:betterment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://svpg.com/the-mba-pathology/">
    <title>The MBA Pathology | Silicon Valley Product Group</title>
    <dc:date>2021-06-15T15:24:46+00:00</dc:date>
    <link>https://svpg.com/the-mba-pathology/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[If you’re not willing to coach and develop these MBA grads to help them unlearn, then you may indeed be better off avoiding MBA hires.  But to me, the prize makes it worth the effort.  These are often very high-potential people.  And I’m not alone.  Several of the top product companies recruit directly out of top business school programs.  They just know they need to “de-program” the students, as one of my friends from Google refers to the unlearning process.]]></description>
<dc:subject>management leadership mbas productmanagement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:e67f7d8251af/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:leadership"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:mbas"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.thekua.com/atwork/2019/02/the-trident-model-of-career-development/">
    <title>The Trident Model of Career Development - patkua@work</title>
    <dc:date>2021-06-09T18:15:36+00:00</dc:date>
    <link>https://www.thekua.com/atwork/2019/02/the-trident-model-of-career-development/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["In my most recent talk, “Talking with Tech Leads,” I explain how, some companies have a two-track career model. Two tracks are great, as they allow for more development and growth in different areas. Most of the research I did seemed to focus on two main tracks. In Silicon Valley they refer to these as Individual Contributor (IC) and Management tracks. I actually don’t think a two-track ladder is enough. This is why I present you the Trident Career Model below."

The Management Track
In this track, people spend a majority of their time (70-80%) on management activities. This still includes leading people, supporting people, managing structures & processes and organising. People in this track must still have some background in the topic they are managing.

Most importantly, their main value add is not necessarily through making decisions related to the specialist field (e.g. system architecture). Instead, they manage the surrounding system & structure to ensure people closest to the work have the best context and information to make better decisions. They provide enough support, time and/or budget to enable others to do what they do best.

Example roles in this track: Engineering Manager, VP Engineering, IT Manager

The Technical Leadership Track
In this track, people spend a majority of their time (70-80%) leading people on a technical topic. People in this track must have relevant hands-on technical skills and experience. They should have good but not necessarily the best skills in the team they are leading. People in this track draw heavily on refined leadership skills to be successful. Classic activities for this role (in the field of software) include:

Establishing a Technical Vision
Managing technical risks
Clarifying/uncovering technical requirements
Ensuring non-technical stakeholders understand technical constraints, trade-offs or important decisions
Growing technical knowledge and cultivating knowledge sharing in and across teams
Example roles in this track: Lead Developer, Tech Lead, Principal Engineer, Software Architect

The True Individual Contributor (IC) Track
In this track, people spend a majority of they time (70-80%) focused on “Executing/Doing”. Software engineers early in their career reflect this very well. This track still requires people to have excellent communication and collaboration skills. People in this track have impact through the deep/detailed knowledge or skills they offer. Most small companies do not need a deep IC track, as there is no need for specialisation. As an organisation grows, they may need more of these roles. The number of these roles will always be smaller than the other two tracks in a well-functioning organisation.

Example roles in this track: DB Specialist, Performing Tuning Specialist, Domain Specialist.]]></description>
<dc:subject>ladders career business management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:885c979e4583/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ladders"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:career"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://newsletter.bringthedonuts.com/p/dual-product-management-career-path">
    <title>It’s Time to Fight for a Dual Product Management Career Path - Bring the Donuts Newsletter</title>
    <dc:date>2021-06-09T16:54:46+00:00</dc:date>
    <link>https://newsletter.bringthedonuts.com/p/dual-product-management-career-path</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[A+ post from Ken Norton]]></description>
<dc:subject>career management people product productmanagement ladders</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:7373ad5ef5f3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:career"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:people"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:product"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ladders"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://slate.com/news-and-politics/2002/04/an-ode-to-managers.html">
    <title>An ode to managers.</title>
    <dc:date>2021-06-05T00:49:17+00:00</dc:date>
    <link>https://slate.com/news-and-politics/2002/04/an-ode-to-managers.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["Turning an opinion into a decision and a decision into a result turns out to be a real skill—like writing, except that most writers (including this one) don’t have it. As a skill, it is partly an innate gift and partly a set of learnable techniques. It may go too far to call business management a science, and most “how-to” business gurus are surely charlatans, but the premise that management is more than just common sense, and worthy of academic study, no longer seems absurd. Even some of the most easily mockable aspects of business life—meetings to plan for meetings, mission statements, PowerPoint slides, to name but three—are not complete jokes."]]></description>
<dc:subject>managers management culture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:7c430883f693/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:managers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.learningbyshipping.com/reaching-peak-meeting-efficiency-f8e47c93317a">
    <title>Reaching Peak Meeting Efficiency. Meetings are undeniably the most… | by Steven Sinofsky | Learning By Shipping</title>
    <dc:date>2021-06-05T00:47:15+00:00</dc:date>
    <link>https://medium.learningbyshipping.com/reaching-peak-meeting-efficiency-f8e47c93317a</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[An opus on meetings, OMG!

"In the course of building a company the most important tool you have to create a culture of shared values is communication and meetings are critical to communication."]]></description>
<dc:subject>management meetings productivity work culture process</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:5c3c1cc4850f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:meetings"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productivity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:work"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:process"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://boz.com/articles/mutual-knowledge">
    <title>Mutual Knowledge</title>
    <dc:date>2021-06-05T00:29:11+00:00</dc:date>
    <link>https://boz.com/articles/mutual-knowledge</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["Meetings are seen as mechanisms to verbally exchange and modify information. That is certainly how they work but it misses what I think is a more fundamental purpose. I posit that if we held a meeting and everything that was said was already known by every individual, the meeting would still be immensely valuable. After such a meeting everyone now knows that everyone else knows the same thing that they do. This is what linguists call mutual knowledge and it is perhaps the most powerful concept I have come across to describe what is required for successful collaboration.

In a state of mutual knowledge, people can speak frankly to advance the state of that knowledge. It serves as a platform to build upon. They can also act with greater independence trusting that they know where their team stands on an issue. By contrast, without mutual knowledge the bulk of time spent in conversation is wasted either speaking indirectly or catching up on cursory details.

If you accept the importance of mutual knowledge, there are a few important implications:

Stable groups matter. I am conservative about varying the membership of meetings or groups because each person gained or lost resets the entire group’s confidence that they are on the same page. Attendance matters a great deal for the same reason. Other attendees can come and go but there must be some core group that identifies as such and shows up consistently. This is why I create a Workplace group (or named email distribution, or slack channel, or whatever) for any recurring meeting I have; to reinforce a sense of shared identity."]]></description>
<dc:subject>culture process management vision alignment teams knowledge meetings</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:18065a2d6d47/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:process"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:vision"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:alignment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:teams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:knowledge"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:meetings"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/swlh/the-silent-meeting-manifesto-v1-189e9e3487eb">
    <title>The Silent Meeting Manifesto v1: Making meeting suck a little less | by David Gasca | The Startup | Medium</title>
    <dc:date>2021-06-05T00:22:39+00:00</dc:date>
    <link>https://medium.com/swlh/the-silent-meeting-manifesto-v1-189e9e3487eb</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["g with 10 other bright colleagues. You’re optimistic about what you might accomplish together. Your optimism quickly fades. At the front of the room the meeting org"]]></description>
<dc:subject>collaboration management meetings documentation silent processes culture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:ef05cc233677/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:meetings"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:silent"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:processes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.thepirasgroup.com/blog/yes-and-versus-yes-but-can-dialog-be-this-simple">
    <title>“Yes, And…” versus “Yes, But…” – Can Dialog be this Simple? | The Piras Group</title>
    <dc:date>2021-05-24T18:24:38+00:00</dc:date>
    <link>https://www.thepirasgroup.com/blog/yes-and-versus-yes-but-can-dialog-be-this-simple</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[video example: https://www.youtube.com/watch?v=cSzCfsGvwj0&t=88s

"Have you ever been explaining a highly valued thought to a colleague and you get an instant response of “Yes, yes, yes, but…?”

In that moment you might feel “discounted” – or hear “what you are saying is not important.”

In daily communications we speak quickly and sometimes react without thought to what we are hearing. Rather than wait, we interject what we think is a better idea or has greater value – the instant “Yes, but… “ Syndrome.

In an effort to facilitate communications especially in meetings, one effective practice is to build ground rules that eliminate the “Yes, but” syndrome and add the “Yes, and” approach. What is the difference?

"Yes, but" communicates judgment and negates what we have heard. Even if the intent is to add our ideas to the communicator’s point of view, it communicates a critical response – what is heard is not good enough and/or the listener has a better idea!

"Yes, but" is heard as adversarial causing someone to feel challenged; whereas "Yes, and" communicates, “I want to build on your idea.” 

It states “in addition” as opposed to “instead of.” One negates – the other is inclusive. "]]></description>
<dc:subject>videos yes but speaking collaboration conflict behavior management productmanagement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:c376f3f6d77d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:videos"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:yes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:but"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:speaking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:conflict"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:behavior"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://queue.acm.org/detail.cfm?id=3454124">
    <title>The SPACE of Developer Productivity - ACM Queue</title>
    <dc:date>2021-04-06T02:31:36+00:00</dc:date>
    <link>https://queue.acm.org/detail.cfm?id=3454124</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["This article explicates several common myths and misconceptions about developer productivity. The most important takeaway from exposing these myths is that productivity cannot be reduced to a single dimension (or metric!). The prevalence of these myths and the need to bust them motivated our work to develop a practical multidimensional framework, because only by examining a constellation of metrics in tension can we understand and influence developer productivity. This framework, called SPACE, captures the most important dimensions of developer productivity: satisfaction and well-being; performance; activity; communication and collaboration; and efficiency and flow. By recognizing and measuring productivity with more than just a single dimension, teams and organizations can better understand how people and teams work, and they can make better decisions.

The article demonstrates how this framework can be used to understand productivity in practice and why using it will help teams better understand developer productivity, create better measures to inform their work and teams, and may positively impact engineering outcomes and developer well-being."]]></description>
<dc:subject>research programming productivity development management work developers</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:771833e0fad3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productivity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:work"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:developers"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://hbr.org/2021/01/the-forgotten-dimension-of-diversity?s=09">
    <title>The Forgotten Dimension of Diversity</title>
    <dc:date>2021-02-23T19:40:08+00:00</dc:date>
    <link>https://hbr.org/2021/01/the-forgotten-dimension-of-diversity?s=09</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>class socioeconomics society management economics</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:53173dc4de50/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:class"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:socioeconomics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:society"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:economics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.investopedia.com/terms/p/porter.asp">
    <title>Porter's 5 Forces Definition</title>
    <dc:date>2021-02-09T01:45:58+00:00</dc:date>
    <link>https://www.investopedia.com/terms/p/porter.asp</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["Understanding Porter's Five Forces
Porter's Five Forces is a business analysis model that helps to explain why various industries are able to sustain different levels of profitability. The model was published in Michael E. Porter's book, "Competitive Strategy: Techniques for Analyzing Industries and Competitors" in 1980.1﻿ The Five Forces model is widely used to analyze the industry structure of a company as well as its corporate strategy. Porter identified five undeniable forces that play a part in shaping every market and industry in the world, with some caveats. The five forces are frequently used to measure competition intensity, attractiveness, and profitability of an industry or market.

Porter's five forces are:

1. Competition in the industry

2. Potential of new entrants into the industry

3. Power of suppliers

4. Power of customers

5. Threat of substitute products"]]></description>
<dc:subject>management strategy competition forces business</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:e33f8cec7a63/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:strategy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:competition"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:forces"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:business"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.nytimes.com/2019/03/28/smarter-living/productivity-isnt-about-time-management-its-about-attention-management.html">
    <title>Productivity Isn’t About Time Management. It’s About Attention Management. - The New York Times</title>
    <dc:date>2021-02-08T18:32:58+00:00</dc:date>
    <link>https://www.nytimes.com/2019/03/28/smarter-living/productivity-isnt-about-time-management-its-about-attention-management.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["A better option is attention management: Prioritize the people and projects that matter, and it won’t matter how long anything takes.

Attention management is the art of focusing on getting things done for the right reasons, in the right places and at the right moments."]]></description>
<dc:subject>management productivity time</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:368d39ecabae/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productivity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:time"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://exp-platform.com/hippo/">
    <title>HiPPO – ExP Platform</title>
    <dc:date>2020-10-08T00:12:24+00:00</dc:date>
    <link>https://exp-platform.com/hippo/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["Q: What is a HiPPO?
A: HiPPO stands for "Highest Paid Person's Opinion."

Jim Barksdale, CEO of Netscape, famously said what could be summarized as Data or HiPPO, when he said "If we have data, let’s look at data. If all we have are opinions, let’s go with mine.""]]></description>
<dc:subject>management opinions data quotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:ccec62609467/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opinions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:quotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.zengestrom.com/blog/2012/09/21-characteristics-of-great-teams.html">
    <title>21 characteristics of great teams :: Zengestrom</title>
    <dc:date>2020-05-20T18:07:31+00:00</dc:date>
    <link>http://www.zengestrom.com/blog/2012/09/21-characteristics-of-great-teams.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["1. A clear, tangible outcome. The best outcomes are widely recognized as important or fantastic.
2. An outrageous vision for the outcome.
3. A leader who can get people to get personally committed to the vision and the outcome.
4. Exceptionally capable people on the team – the best talent available.
5. A leader that the team respects.
6. A leader who gives the team members the information, recognition and latitude they need to deliver the outcome.
7. A leader who keeps the team focused without micro managing it.
8. A shabby workplace with access to all the equipment, materials, tools and training the team needs to deliver the outcome.
9. Team is protected from bureaucracy of the sponsor/sponsor organization.
10. The workplace enables collaboration.
11. Team is insulated from distractions.
12. There is one focus for the team – the outcome.
13. Team members have responsibilities that are aligned to their expertise, interests, and capabilities.
14. Team members are willing to work on what needs to be worked on when it needs to be worked on.
15. People don’t always get along but everyone wants to achieve the outcome so this common desire transcends individual conflicts.
16. Team members know that each team member has been personally selected for the team because he or she is most able to get the job done.
17. Failure is accepted; incompetence and disloyalty is not.
18. The team has a common enemy.
19. The team believes they are on a mission from God.
20. The team doesn’t realize their mission is impossible and impractical.
21. The team is physically separated from those not on the team but retains a linkage with the ultimate sponsors of the mission generally via the team leader(s)."]]></description>
<dc:subject>collaboration management leadership teams culture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:514719913b26/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:leadership"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:teams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>