{"id":4712,"date":"2026-11-21T07:59:50","date_gmt":"2026-11-21T07:59:50","guid":{"rendered":"https:\/\/dataopsschool.com\/blog\/?p=4712"},"modified":"2026-11-21T08:01:50","modified_gmt":"2026-11-21T08:01:50","slug":"eight-data-engineering-goals-to-reread-monthly","status":"publish","type":"post","link":"https:\/\/dataopsschool.com\/blog\/eight-data-engineering-goals-to-reread-monthly\/","title":{"rendered":"Eight Data Engineering Goals to Reread Every Month"},"content":{"rendered":"<p>Data engineering goals have a short shelf life. A pipeline target that made sense when the warehouse held three sources looks silly when it holds thirty. A skill you planned to learn this quarter may have been made irrelevant by a platform decision made in a meeting you were not in. The cure is unglamorous: once a month, sit down with your written goals and reread them. This list gives you eight goal types worth checking every time, each with a quick test and a typical fix.<\/p>\n<p>Whether you are a solo analyst moving into data engineering or a lead on a small team, the routine is the same. Block thirty minutes, open the list and go line by line. Below are the eight items I would put on that list for a DataOps-minded practitioner.<\/p>\n<h2>1. The data quality goal<\/h2>\n<p>Something like &#8220;stop bad rows reaching the dashboards&#8221; is the most common goal on a data team&#8217;s list, and the one that drifts most quietly. The test: has the kind of bad data you see changed? Early on, it is nulls and duplicates. Later it is late-arriving records and silent schema changes upstream.<\/p>\n<p>The typical fix is to narrow the goal. Instead of &#8220;improve quality everywhere,&#8221; pick the two tables that feed the most-used reports and write checks for those only. If you want a refresher on structuring checks, there is a hands-on walkthrough in <a href=\"https:\/\/dataopsschool.com\/blog\/great-expectations-for-data-validation-in-dataops-a-practical-guide\/\">a practical write-up on validating datasets inside DataOps workflows<\/a>.<\/p>\n<h2>2. The freshness goal<\/h2>\n<p>&#8220;Have yesterday&#8217;s numbers ready by 8 a.m.&#8221; is a goal that depends on who is reading. If the executive who wanted it has moved on, or the reporting day has shifted, your tight deadline may be burning effort for no reader. The test is simple: ask one actual consumer when they last needed the data at that time. If nobody can say, loosen the target and take the on-call pressure off.<\/p>\n<h2>3. The cost goal<\/h2>\n<p>Storage and compute targets often get written during a budget scare and then forgotten. Reread the figure, in your head or on paper, and ask whether the workload has grown past what the goal assumed. Do not chase a number that was set for a smaller warehouse. Either update it or make the goal about a trend, such as &#8220;no query class gets more expensive month over month without a reason.&#8221;<\/p>\n<h2>4. The documentation goal<\/h2>\n<p>Nearly everyone has &#8220;document the pipelines&#8221; somewhere on the list. The problem is that it is shapeless. At each reread, replace it with a concrete slice: this month, the three jobs that page someone most often. When that slice is done, the next slice takes its place. A goal that never finishes is a goal that never gets worked on.<\/p>\n<h2>5. The tooling-upgrade goal<\/h2>\n<p>Goals such as &#8220;migrate transformations to the new framework&#8221; tend to be written in a burst of optimism. Check what has changed since: is the migration still blocked by the same dependency, or did the team make a different choice? If the aim is still live, break it into a first small model or job to move. For context on how that style of transformation work is usually structured, <a href=\"https:\/\/dataopsschool.com\/blog\/master-data-transformations-with-dbt-in-modern-dataops-pipelines\/\">this guide to building transformation layers in modern DataOps pipelines<\/a> covers the shape of it.<\/p>\n<h2>6. The monitoring and alert goal<\/h2>\n<p>The test here is blunt: did anyone act on an alert this month? If the answer is no, the goal is probably either to reduce noise or to add a missing signal, and the old wording &#8220;add more monitoring&#8221; is not helping. Rewrite it as one specific gap, such as &#8220;know within an hour if a nightly load silently loads zero rows.&#8221;<\/p>\n<h2>7. The skills goal<\/h2>\n<p>Personal goals deserve the same treatment as pipeline ones. If you wrote &#8220;learn streaming&#8221; in January, but your team has no streaming workload and none is planned, the goal may be a pleasant hobby and not a priority. That is fine, but label it honestly. Alternatively, swap it for the skill your current projects keep asking for, such as testing practices, orchestration or plain SQL performance tuning.<\/p>\n<p>A small aside for people who study alongside work: <a href=\"https:\/\/aircrewu.com\/\">AirCrewU, a website for an online learning platform serving aviation professionals<\/a>, which shows how a single profession can have a whole catalogue of study built around it. Whatever the field, the habit is identical: each month, ask whether the course, book or tutorial you planned still earns the hours you set aside for it, and be willing to swap it for something that fits this month better than it fit last month.<\/p>\n<h2>8. The handover goal<\/h2>\n<p>This one is easy to miss: &#8220;make sure someone else can run this.&#8221; People write it after a close call and never revisit it. Reread it by asking who else touched the pipeline last month. If the answer is nobody, the goal is still very much alive, and the first step might be as small as one colleague shadowing a single load run.<\/p>\n<h2>What a retired goal looks like on paper<\/h2>\n<p>People hesitate to cross things out, so here is a concrete picture. A retired goal does not vanish. It moves to the bottom of the page under a heading such as &#8220;Not now,&#8221; with a date and one sentence explaining why. When a new quarter starts or a project changes shape, you scan that section first. Occasionally a goal comes back, usually in a better form than the original. More often you read the line, nod and delete it for good, with no guilt attached.<\/p>\n<p>The same idea works for goals you have reshaped. Keep the old wording beside the new one for a single month. Seeing both lines together makes it obvious whether you tightened the aim or just dodged it.<\/p>\n<h2>How to run the monthly reread in thirty minutes<\/h2>\n<ol>\n<li><strong>Print or open the list.<\/strong> Everything in one place, no scattered notes.<\/li>\n<li><strong>Read each line and ask one question:<\/strong> would I write this goal again today? If yes, it stays. If it is close, reword it. If not, cross it out.<\/li>\n<li><strong>Look for evidence.<\/strong> A goal with no activity for a month is not automatically dead, but it deserves a sentence of explanation.<\/li>\n<li><strong>Cap the list.<\/strong> Five active goals is a sensible ceiling for one person, and a small team can manage a few more.<\/li>\n<li><strong>Write the next action for each survivor.<\/strong> One concrete step, small enough to start this week.<\/li>\n<\/ol>\n<h2>Three traps to avoid<\/h2>\n<p>The first trap is rewriting goals into vague language to avoid admitting they stalled. &#8220;Improve data culture&#8221; is not an upgrade on &#8220;write checks for the orders table.&#8221; The second is hoarding: if the list grows every month and shrinks never, you are collecting, not reviewing. The third is reviewing alone and never telling anyone. Posting the three changes you made where teammates will see them gives people a chance to object if a retired goal still matters to them.<\/p>\n<h2>A worked miniature<\/h2>\n<p>Suppose your list has the eight items above and you reread it on the first of the month. Quality stays but narrows to two tables. Freshness loosens by an hour. Cost becomes a trend goal. Documentation shrinks to three jobs. The tooling migration is paused for a quarter with a note on why. Monitoring becomes a single gap. The skills goal swaps streaming for orchestration. Handover stays as written, with a first shadowing session booked. Eight lines, five changes, thirty minutes, and you have a list that matches the work you will actually do.<\/p>\n<p>That is the whole method. Data work rewards people who notice when the ground shifts, and a regular reread turns noticing into a habit. Put the date in your calendar now, before the month fills up.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Eight common data team goals, from quality checks to handover, each with a quick test and a typical fix to use at your monthly reread of the list.<\/p>\n","protected":false},"author":6,"featured_media":4713,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[814],"tags":[],"class_list":["post-4712","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dataops"],"_links":{"self":[{"href":"https:\/\/dataopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/4712","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dataopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dataopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dataopsschool.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/dataopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=4712"}],"version-history":[{"count":1,"href":"https:\/\/dataopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/4712\/revisions"}],"predecessor-version":[{"id":4863,"href":"https:\/\/dataopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/4712\/revisions\/4863"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dataopsschool.com\/blog\/wp-json\/wp\/v2\/media\/4713"}],"wp:attachment":[{"href":"https:\/\/dataopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=4712"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dataopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=4712"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dataopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=4712"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}