Skip to content

Commit

Permalink
deploy: 201e923
Browse files Browse the repository at this point in the history
  • Loading branch information
github-actions[bot] committed Jul 25, 2023
1 parent 3fd7167 commit b719120
Show file tree
Hide file tree
Showing 3 changed files with 21 additions and 28 deletions.
22 changes: 9 additions & 13 deletions feed.xml
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
<id>https://leebyron.com/til/feed.xml</id>
<link rel="self" type="application/atom+xml" href="https://leebyron.com/til/feed.xml"/>
<link rel="alternate" type="text/html" href="https://leebyron.com/til/"/>
<updated>2023-07-24T23:39:52.000+00:00</updated>
<updated>2023-07-25T22:37:12.000+00:00</updated>
<title>Lee Byron / til</title>
<subtitle>
Things I've Learned: brief blurbs on miscellaneous matter.
Expand All @@ -19,21 +19,20 @@
<id>https://leebyron.com/til/intent/</id>
<link rel="alternate" type="text/html" href="https://leebyron.com/til/intent/"/>
<published>2023-07-24T12:02:27.000-07:00</published>
<updated>2023-07-24T23:39:52.000+00:00</updated>
<updated>2023-07-25T22:37:12.000+00:00</updated>
<title>radiate intent</title>
<author>
<name>Lee Byron</name>
<uri>https://leebyron.com</uri>
</author>
<category term="leadership"/>
<category term="management"/>
<content type="html"><![CDATA[<blockquote>
<p>
It’s easier to ask forgiveness than it is to get permission.<br>— Grace Hopper<a href="#fn:1" id="fn:1.ref" data-footnote-ref aria-label="note"><sup>1</sup></a>
</p>
</blockquote>
<p>
This is classic advice when operating in a large organization. You see a problem to be solved, have a bold solution in mind, and have everything necessary to take action, but there will be very real costs felt broadly. You think the tradeoff is worth it, but will your higher-ups agree? Or will they simply blame you for the costs without appreciating the problem solved?
This is classic advice when operating in a large organization. There’s a problem to be solved, you have a bold solution in mind and have everything necessary to take action, but there will be very real costs felt broadly. You think the tradeoff is worth it, but will your higher-ups agree?
</p>
<p>
You likely have the best information on the decision but might assume you need permission to incur the costs. If your higher-ups assume the same then analysis paralysis sets in. If it’s a good idea, <em>go ahead and do it</em>. Grace Hopper encouraged a bias to action; to do the right thing for the org whether or not they know it to be. If you’re wrong or get flak for the costs: ask forgiveness; you acted in good faith.
Expand All @@ -42,26 +41,23 @@
This good advice is missing one critical thing: <em>radiating intent</em>.
</p>
<p>
While “forgiveness, not permission” considers what you’re asking, it says nothing about what you’re telling. If you anticipate needing to ask forgiveness after taking action then its best to get ahead of it by explaining the decision clearly immediately after you’ve made it. Even better, explain <em>before</em> you act then radiate it: share far and wide.
</p>
<p>
<img src="../media/222f597868763d3e.svg" alt="intent">
<img src="../media/222f597868763d3e.svg" alt="intention is telling not asking">
</p>
<p>
With this in mind it becomes clear that rather than shifting from asking before to after you act, you should instead shift from asking to telling. Don’t seek permission, seek to inform. Radiating intent is telling what you will do before you do it.
Rather than shifting from permission before to forgiveness after, shift from asking permission to telling as many as you can about your intention. Radiating intent is telling what you will do before you do it loudly and clearly so that no one will be surprised.
</p>
<p>
Elizabeth Ayer, in her <a href="https://medium.com/@ElizAyer/dont-ask-forgiveness-radiate-intent-d36fd22393a3" target="_blank">excellent article</a> on radiating intent explains why it’s superior to asking forgiveness (which I’ve editorialized):
</p>
<ol start="1">
<li>
<p>
Invites participation from those with critical info or desire to help
Invites participation from those with critical info or a desire to help.
</p>
</li>
<li>
<p>
If wrong it gives a chance for someone to stop you as you begin. You’re not left waiting as when asking permission.
If wrong it gives a chance for someone to stop you, however you’re not left waiting as when asking permission.
</p>
</li>
<li>
Expand Down Expand Up @@ -89,7 +85,7 @@
<ul>
<li>
<p>
<strong>Write it down.</strong> Start with a short description of what you intend to do, and why. Keep the bottom line at the top. Expand your thinking from there: document assumptions, options and trade-offs. This will help you communicate clearly, create a single source of truth, and avoid repeating yourself.
<strong>Write it down.</strong> Start with a short description of what you intend to do, and why. Don’t bury the lede. Expand your thinking from there: document assumptions, options and trade-offs. This will help you communicate clearly, create a single source of truth, and avoid repeating yourself.
</p>
</li>
<li>
Expand All @@ -109,7 +105,7 @@
</li>
<li>
<p>
<strong>Scale volume with impact.</strong> Radiating intent matters most when those around you will be impacted most. Share broader more frequently in situations that demand it, and narrower otherwise.
<strong>Scale volume with impact.</strong> Radiating intent matters most when those around you will be impacted most. Share broader and more frequently in situations that demand it, and narrower otherwise.
</p>
</li>
</ul>
Expand Down
25 changes: 11 additions & 14 deletions intent/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -7,12 +7,12 @@
<meta property="og:title" content="til / radiate intent — Lee Byron">
<meta property="og:description" content="It’s easier to ask forgiveness than it is to get permission.— Grace Hopper">
<meta property="og:image" content="https://leebyron.com/til/media/222f597868763d3e.svg">
<meta property="og:image:alt" content="intent">
<meta property="og:image:alt" content="intention is telling not asking">
<meta property="og:type" content="article">
<meta property="article:author:first_name" content="Lee">
<meta property="article:author:last_name" content="Byron">
<meta property="article:published_time" content="2023-07-24T12:02:27.000-07:00">
<meta property="article:modified_time" content="2023-07-24T23:39:52.000+00:00">
<meta property="article:modified_time" content="2023-07-25T22:37:12.000+00:00">
<meta name="twitter:card" content="summary">
<meta name="twitter:creator" content="@leeb">
<script type="application/ld+json">
Expand All @@ -29,8 +29,8 @@
},
"url": "https://leebyron.com/til/intent/",
"datePublished": "2023-07-24T12:02:27.000-07:00",
"dateModified": "2023-07-24T23:39:52.000+00:00",
"keywords": "leadership, management",
"dateModified": "2023-07-25T22:37:12.000+00:00",
"keywords": "leadership",
"isPartOf": "https://leebyron.com/til/",
"license": "https://creativecommons.org/licenses/by/4.0/"
}
Expand Down Expand Up @@ -62,7 +62,7 @@ <h1>
</p>
</blockquote>
<p>
This is classic advice when operating in a large organization. You see a problem to be solved, have a bold solution in mind, and have everything necessary to take action, but there will be very real costs felt broadly. You think the tradeoff is worth it, but will your higher-ups agree? Or will they simply blame you for the costs without appreciating the problem solved?
This is classic advice when operating in a large organization. There’s a problem to be solved, you have a bold solution in mind and have everything necessary to take action, but there will be very real costs felt broadly. You think the tradeoff is worth it, but will your higher-ups agree?
</p>
<p>
You likely have the best information on the decision but might assume you need permission to incur the costs. If your higher-ups assume the same then analysis paralysis sets in. If it’s a good idea, <em>go ahead and do it</em>. Grace Hopper encouraged a bias to action; to do the right thing for the org whether or not they know it to be. If you’re wrong or get flak for the costs: ask forgiveness; you acted in good faith.
Expand All @@ -71,26 +71,23 @@ <h1>
This good advice is missing one critical thing: <em>radiating intent</em>.
</p>
<p>
While “forgiveness, not permission” considers what you’re asking, it says nothing about what you’re telling. If you anticipate needing to ask forgiveness after taking action then its best to get ahead of it by explaining the decision clearly immediately after you’ve made it. Even better, explain <em>before</em> you act then radiate it: share far and wide.
<img src="../media/222f597868763d3e.svg" alt="intention is telling not asking">
</p>
<p>
<img src="../media/222f597868763d3e.svg" alt="intent">
</p>
<p>
With this in mind it becomes clear that rather than shifting from asking before to after you act, you should instead shift from asking to telling. Don’t seek permission, seek to inform. Radiating intent is telling what you will do before you do it.
Rather than shifting from permission before to forgiveness after, shift from asking permission to telling as many as you can about your intention. Radiating intent is telling what you will do before you do it loudly and clearly so that no one will be surprised.
</p>
<p>
Elizabeth Ayer, in her <a href="https://medium.com/@ElizAyer/dont-ask-forgiveness-radiate-intent-d36fd22393a3" target="_blank">excellent article</a> on radiating intent explains why it’s superior to asking forgiveness (which I’ve editorialized):
</p>
<ol start="1">
<li>
<p>
Invites participation from those with critical info or desire to help
Invites participation from those with critical info or a desire to help.
</p>
</li>
<li>
<p>
If wrong it gives a chance for someone to stop you as you begin. You’re not left waiting as when asking permission.
If wrong it gives a chance for someone to stop you, however you’re not left waiting as when asking permission.
</p>
</li>
<li>
Expand Down Expand Up @@ -118,7 +115,7 @@ <h3 id="addendum-how-to-radiate-intent">
<ul>
<li>
<p>
<strong>Write it down.</strong> Start with a short description of what you intend to do, and why. Keep the bottom line at the top. Expand your thinking from there: document assumptions, options and trade-offs. This will help you communicate clearly, create a single source of truth, and avoid repeating yourself.
<strong>Write it down.</strong> Start with a short description of what you intend to do, and why. Don’t bury the lede. Expand your thinking from there: document assumptions, options and trade-offs. This will help you communicate clearly, create a single source of truth, and avoid repeating yourself.
</p>
</li>
<li>
Expand All @@ -138,7 +135,7 @@ <h3 id="addendum-how-to-radiate-intent">
</li>
<li>
<p>
<strong>Scale volume with impact.</strong> Radiating intent matters most when those around you will be impacted most. Share broader more frequently in situations that demand it, and narrower otherwise.
<strong>Scale volume with impact.</strong> Radiating intent matters most when those around you will be impacted most. Share broader and more frequently in situations that demand it, and narrower otherwise.
</p>
</li>
</ul>
Expand Down
2 changes: 1 addition & 1 deletion test/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -242,7 +242,7 @@ <h2 id="here-is-a-sub-header">
<p>
And one with an expression and fragment:
</p>
<div style="rgb(60.95726786965524, 226.49067413750424, 195.95460674952005)">
<div style="rgb(242.84380021849378, 119.12574127396279, 137.23310334031373)">
</div>
<p>
And here is an inline expression 12!
Expand Down

0 comments on commit b719120

Please sign in to comment.