<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Technical-Manager on Keith Kee KW</title>
		<link>https://keithkeekw.github.io/tags/technical-manager/</link>
		<description>Recent content in Technical-Manager on Keith Kee KW</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sun, 26 Jul 2026 08:00:00 +0800</lastBuildDate>
		
			<atom:link href="https://keithkeekw.github.io/tags/technical-manager/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>The New Technical Manager Manual</title>
				<link>https://keithkeekw.github.io/posts/2026-07-26-new-technical-manager-manual/</link>
				<pubDate>Sun, 26 Jul 2026 08:00:00 +0800</pubDate>
				<guid>https://keithkeekw.github.io/posts/2026-07-26-new-technical-manager-manual/</guid>
				<description>&lt;p&gt;You just became a technical manager. Congratulations — and good luck.&lt;/p&gt;&#xA;&lt;p&gt;Nobody hands you a manual when you get promoted. One day you fix things. The next, you&amp;rsquo;re responsible for the people who fix things — plus the process, escalations, headcount planning, and the emotional wellbeing of a team that expects you to have answers.&lt;/p&gt;&#xA;&lt;p&gt;The skills that got you promoted — technical depth, personal output, being the go-to fixer — are not the skills that will make you successful as a manager. You need a different toolkit. This is the manual I wish I had.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
