<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Management on Harlan D. Harris</title><link>https://harlanh.tech/tags/management/</link><description>Recent content in Management on Harlan D. Harris</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>harlan.harris@gmail.com (Harlan Harris)</managingEditor><webMaster>harlan.harris@gmail.com (Harlan Harris)</webMaster><lastBuildDate>Mon, 13 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://harlanh.tech/tags/management/index.xml" rel="self" type="application/rss+xml"/><item><title>You Don't Need a Search Engineer; You Need a Search Scientist</title><link>https://harlanh.tech/2026/04/you-dont-need-a-search-engineer-you-need-a-search-scientist/</link><pubDate>Mon, 13 Apr 2026 00:00:00 +0000</pubDate><author>harlan.harris@gmail.com (Harlan Harris)</author><guid>https://harlanh.tech/2026/04/you-dont-need-a-search-engineer-you-need-a-search-scientist/</guid><description>
&lt;p&gt;Say you're an Engineering Manager or a Product Manager, responsible for a business-critical
search system on a website. Maybe e-commerce, maybe a marketplace, maybe something else.
Search is sort of working, it doesn't crash, and it's fast, but there's a
feeling that &amp;quot;search isn't great&amp;quot;, and you've been tasked with finding someone to help.
Your first instinct, or that of your VP, might be some version of: “we need to hire a search engineer.”&lt;/p&gt;</description></item><item><title>How Search and AI Product Teams are Different</title><link>https://harlanh.tech/2026/02/search-and-ai-teams-are-different/</link><pubDate>Tue, 03 Feb 2026 00:00:00 +0000</pubDate><author>harlan.harris@gmail.com (Harlan Harris)</author><guid>https://harlanh.tech/2026/02/search-and-ai-teams-are-different/</guid><description>
&lt;p&gt;Engineering leadership knows the standard playbook for product teams: the &lt;a href="https://www.producttalk.org/product-trios/"&gt;Product Trio&lt;/a&gt;, the &lt;a href="https://productschool.com/blog/product-fundamentals/spotify-model-scaling-agile"&gt;Spotify model&lt;/a&gt;, &lt;a href="https://productschool.com/blog/product-strategy/outcome-based-roadmap"&gt;outcome-based roadmaps&lt;/a&gt;, and so on. I've seen teams adopt these practices and still struggle when they add responsibility for advanced algorithms -- search, recommendations, predictive modeling, or generative AI -- without changing how the team is led. The processes and role expectations that work for a typical product team break down when the domain is heavily algorithmic. This post pulls together what I've learned and what others have written about building teams that own these systems.&lt;/p&gt;</description></item><item><title>Staff Data Scientist: Comments on Will Larson's Staff Engineer Book</title><link>https://harlanh.tech/2022/05/staff-data-scientist-comments-on-will-larson-s-staff-engineer-book/</link><pubDate>Fri, 27 May 2022 00:00:00 +0000</pubDate><author>harlan.harris@gmail.com (Harlan Harris)</author><guid>https://harlanh.tech/2022/05/staff-data-scientist-comments-on-will-larson-s-staff-engineer-book/</guid><description>
&lt;p&gt;I recently read Will Larson's excellent book &lt;a href="https://staffeng.com/book"&gt;Staff Engineer: Leadership
beyond the management track&lt;/a&gt;. Larson covers
the individual contributor (IC, not management) roles that software
engineers fill after they are promoted past Senior Software Engineer,
with titles like Staff and Principal (&amp;quot;Staff-plus&amp;quot;). In the book, he
synthesizes his own experience and the experiences of a number of other
Staff-plus engineers, and provides great insights into how to get
promoted to that level, and how to succeed at it. Great book -- you
should read it.&lt;/p&gt;</description></item><item><title>Thoughts on Managing Data Science Team Workstreams (and a Shiny app)</title><link>https://harlanh.tech/2016/01/thoughts-on-managing-data-science-team-workstreams-and-a-shiny-app/</link><pubDate>Thu, 28 Jan 2016 00:00:00 +0000</pubDate><author>harlan.harris@gmail.com (Harlan Harris)</author><guid>https://harlanh.tech/2016/01/thoughts-on-managing-data-science-team-workstreams-and-a-shiny-app/</guid><description>
&lt;p&gt;&lt;em&gt;&lt;a href="https://medium.com/@HarlanH/thoughts-on-managing-data-science-team-workstreams-and-a-shiny-app-f2b25549946f"&gt;This post was originally published on Medium&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;
&lt;a href="https://x.com/josh_wills/status/198093512149958656"&gt;
View this post on X (josh_wills)
&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;There are different types of data scientists, with different backgrounds and career paths. With Sean Murphy and Marck Vaisman, I wrote an article about this for O’Reilly a few years back, based on survey research we’d done. &lt;a href="http://shop.oreilly.com/product/0636920029014.do"&gt;Download a copy&lt;/a&gt;, if you haven’t read it. This idea is now pretty well established, but I want to talk about a related issue, which is that the &lt;em&gt;type of work&lt;/em&gt;that Data Science teams do varies a lot, and that managing those types of work can be an interesting challenge.&lt;/p&gt;</description></item><item><title>Building a Complementary Data Science Team</title><link>https://harlanh.tech/2015/11/building-a-complementary-data-science-team/</link><pubDate>Mon, 23 Nov 2015 00:00:00 +0000</pubDate><author>harlan.harris@gmail.com (Harlan Harris)</author><guid>https://harlanh.tech/2015/11/building-a-complementary-data-science-team/</guid><description>
&lt;p&gt;&lt;em&gt;&lt;a href="https://medium.com/@HarlanH/building-a-complementary-data-science-team-7b38d39d1880"&gt;This post was originally published on Medium&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;I’m the Director of Data Science at EAB, a firm that provides best-practices research and enterprise software for colleges and universities. My team is responsible for the predictive models and other advanced analytics that are part of the Student Success Collaborative product that’s used by academic advisors and other campus leadership. We’re hiring data scientists, and I wanted to publicly say a few things about the roles we have advertised. (Note that EAB is part of a public company and is in a competitive market, so there are obviously things I’m not saying!)&lt;/p&gt;</description></item></channel></rss>