Skip to content

Commit

Permalink
deploy: 16699d2
Browse files Browse the repository at this point in the history
  • Loading branch information
github-actions[bot] committed Jul 24, 2023
1 parent 0b191af commit 9f226b7
Show file tree
Hide file tree
Showing 3 changed files with 25 additions and 25 deletions.
24 changes: 12 additions & 12 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-24T22:20:39.000+00:00</updated>
<updated>2023-07-24T22:37:54.000+00:00</updated>
<title>Lee Byron / til</title>
<subtitle>
Things I've Learned: brief blurbs on miscellaneous matter.
Expand All @@ -19,7 +19,7 @@
<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-24T22:20:39.000+00:00</updated>
<updated>2023-07-24T22:37:54.000+00:00</updated>
<title>radiate intent</title>
<author>
<name>Lee Byron</name>
Expand All @@ -33,25 +33,25 @@
</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 larger problem solved?
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 larger problem solved?
</p>
<p>
In this position you likely have the best information on the decision but may assume you need permission to incur the costs. If your higher-ups assume the same then analysis paralysis sets in and it’s unlikely you’ll hear anything new that changes your original assessment. 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.
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.
</p>
<p>
This is good advice missing one critical thing: <em>radiating intent</em>.
This 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 the decision <em>before</em> you make it then radiate it, sharing it far and wide.
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">
</p>
<p>
With this frame in mind it becomes more clear that rather than shifting your ask from before until after you act, instead shift from asking to telling.
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.
</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 (or permission), which I’ve editorialized:
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 a superior approach (which I’ve editorialized):
</p>
<ul>
<li>
Expand All @@ -61,7 +61,7 @@
</li>
<li>
<p>
In case you’re wrong, it gives a chance for someone to stop you <em>before</em> hand
If you’re wrong, it gives a chance for someone to stop you <em>before</em> hand
</p>
</li>
<li>
Expand All @@ -71,17 +71,17 @@
</li>
<li>
<p>
Sets the example that bold action and taking risks is encouraged from everyone, not just organizational higher-ups.
You keep responsibility and own the outcome, good or bad. Doesn’t transfer blame as seeking permission does.
</p>
</li>
<li>
<p>
Keeps responsibility on the actor who owns the outcome good or bad. Doesn’t transfer blame as seeking permission does.
Sets the example that bold action and taking risks is encouraged from everyone, not just organizational higher-ups.
</p>
</li>
</ul>
<p>
If it’s a good idea, go ahead and do it. Own the outcome. <em>Radiate intent!</em>
If it’s a good idea, go ahead and do it. But loudly say what you are doing along the way. <em>Radiate intent!</em>
</p>
<section data-footnotes aria-label="footnotes">
<ol>
Expand Down
24 changes: 12 additions & 12 deletions intent/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@
<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-24T22:20:39.000+00:00">
<meta property="article:modified_time" content="2023-07-24T22:37:54.000+00:00">
<meta name="twitter:card" content="summary">
<meta name="twitter:creator" content="@leeb">
<script type="application/ld+json">
Expand All @@ -29,7 +29,7 @@
},
"url": "https://leebyron.com/til/intent/",
"datePublished": "2023-07-24T12:02:27.000-07:00",
"dateModified": "2023-07-24T22:20:39.000+00:00",
"dateModified": "2023-07-24T22:37:54.000+00:00",
"keywords": "leadership, management",
"isPartOf": "https://leebyron.com/til/",
"license": "https://creativecommons.org/licenses/by/4.0/"
Expand Down Expand Up @@ -62,25 +62,25 @@ <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 larger problem solved?
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 larger problem solved?
</p>
<p>
In this position you likely have the best information on the decision but may assume you need permission to incur the costs. If your higher-ups assume the same then analysis paralysis sets in and it’s unlikely you’ll hear anything new that changes your original assessment. 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.
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.
</p>
<p>
This is good advice missing one critical thing: <em>radiating intent</em>.
This 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 the decision <em>before</em> you make it then radiate it, sharing it far and wide.
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">
</p>
<p>
With this frame in mind it becomes more clear that rather than shifting your ask from before until after you act, instead shift from asking to telling.
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.
</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 (or permission), which I’ve editorialized:
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 a superior approach (which I’ve editorialized):
</p>
<ul>
<li>
Expand All @@ -90,7 +90,7 @@ <h1>
</li>
<li>
<p>
In case you’re wrong, it gives a chance for someone to stop you <em>before</em> hand
If you’re wrong, it gives a chance for someone to stop you <em>before</em> hand
</p>
</li>
<li>
Expand All @@ -100,17 +100,17 @@ <h1>
</li>
<li>
<p>
Sets the example that bold action and taking risks is encouraged from everyone, not just organizational higher-ups.
You keep responsibility and own the outcome, good or bad. Doesn’t transfer blame as seeking permission does.
</p>
</li>
<li>
<p>
Keeps responsibility on the actor who owns the outcome good or bad. Doesn’t transfer blame as seeking permission does.
Sets the example that bold action and taking risks is encouraged from everyone, not just organizational higher-ups.
</p>
</li>
</ul>
<p>
If it’s a good idea, go ahead and do it. Own the outcome. <em>Radiate intent!</em>
If it’s a good idea, go ahead and do it. But loudly say what you are doing along the way. <em>Radiate intent!</em>
</p>
<section data-footnotes aria-label="footnotes">
<ol>
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(73.28075569938339, 133.68205987345385, 66.12437262861869)">
<div style="rgb(89.17141932886345, 101.45858142744267, 103.28436631818393)">
</div>
<p>
And here is an inline expression 12!
Expand Down

0 comments on commit 9f226b7

Please sign in to comment.