{"id":17229,"date":"2026-03-05T14:41:05","date_gmt":"2026-03-05T14:41:05","guid":{"rendered":"https:\/\/blog.tubikstudio.com\/?p=17229"},"modified":"2026-04-06T12:24:20","modified_gmt":"2026-04-06T12:24:20","slug":"farmsense-case-study","status":"publish","type":"post","link":"https:\/\/tubikstudio.com\/blog\/farmsense-case-study\/","title":{"rendered":"FarmSense Case Study: Fields, Sensors, and System Thinking"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">Most dashboards are built for people sitting still. FarmSense is built for people who move\u2014across acres, across uncertainty, across seasons that refuse to behave.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Growers wake up before sunrise, walk fields that stretch further than your eye wants to focus, and make decisions that cost real money if they\u2019re late by even a day. Pest activity doesn\u2019t wait for clean UI. Heat accumulates. Insects develop. Thresholds are crossed quietly.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">FarmSense monitors that invisible escalation. It captures real-time sensor data\u2014insect counts, environmental shifts, thermal accumulation\u2014and translates it into signals growers can act on before crop loss becomes visible from the highway.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Our mission for this project sounded deceptively simple: turn entomology, telemetry, and environmental modeling into a system where a grower can open the dashboard and immediately understand three things\u2014what\u2019s happening, how urgent it is, and what to do next. The reality was a dense system of relationships, edge cases, and decisions under pressure.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Here\u2019s how we made a dense agricultural ecosystem feel navigable\u2014and reliable\u2014in real time. Keep reading!<\/span><\/p>\n<p><iframe loading=\"lazy\" title=\"DR_fields04_new 2_1 (1)\" src=\"https:\/\/player.vimeo.com\/video\/1086310014?dnt=1&amp;app_id=122963\" width=\"500\" height=\"286\" frameborder=\"0\" allow=\"autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\"><\/iframe><\/p>\n<h2><strong>About the Client<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">FarmSense is a U.S.-based AgTech company focused on data-driven pest management. Their hardware captures insect activity and environmental data. Their software interprets it. Together, they aim to reduce crop loss while lowering unnecessary pesticide use.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The client team included developers who deeply understood the domain logic. Not \u201cwe skimmed the documentation\u201d familiarity\u2014actual fluency in insect growth cycles, sensor states, and device telemetry. That changed the rhythm of the project.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">We weren\u2019t designing in isolation and then waiting for validation. We were on calls dissecting edge cases: what happens when a sensor goes offline mid-cycle? How should thermal-day accumulation behave when temperature spikes overnight? Which insect thresholds matter per crop?<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Direct communication with the engineer became one of the most valuable tools in the project. It shortened feedback loops. It prevented decorative assumptions. It grounded the interface in reality.<\/span><\/p>\n<h2><strong>The Brief<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">The goal was to design a comprehensive dashboard for complex agricultural sensor data. We needed an interface capable of holding a high cognitive load without overwhelming users with agricultural jargon or raw telemetry. Some users were comfortable with data. Others cared about one thing: \u201cDo I need to act today?\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">At the same time, the UI had to reflect FarmSense\u2019s brand identity. It was a field product, and it needed to feel credible, precise, and durable\u2014like equipment you trust.<\/span><\/p>\n<h3><strong>Challenges Identified Up Front<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">Translating scientific and entomological insights into digestible UI elements was the first friction point. Insects develop faster with more heat. That\u2019s obvious to entomologists. In UI, that logic has to become visible, trackable, and urgent without becoming cryptic.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Then came object relationships. Devices belonged to organizations. Organizations had administrators. Sensors lived in fields. Fields were linked to crops. Crops were vulnerable to specific insects. Insects had growth stages driven by thermal days. Each entity had states and thresholds.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Instead of simply designing screens, we were mapping a living system.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">And then there were real-world constraints. Pest outbreaks don\u2019t politely escalate; field conditions vary; users might check data in an office chair or while standing between crop rows with limited connectivity. Literacy levels around data vary just as widely.<\/span><\/p>\n<p><iframe loading=\"lazy\" title=\"2\" src=\"https:\/\/player.vimeo.com\/video\/1086309993?dnt=1&amp;app_id=122963\" width=\"500\" height=\"286\" frameborder=\"0\" allow=\"autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\"><\/iframe><\/p>\n<h2><strong>Research &amp; Functional Architecture<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">We began with market research and functional analysis. What tools are growers already using? Where do they struggle? What does \u201ctoo much information\u201d actually look like in agricultural software?<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Then we mapped the product architecture. Fields, sensors, device states, insect profiles, crops. We diagrammed relationships like we were building a subway map\u2014making sure no line crossed without reason. At the same time, the client already had an earlier version of the product in place. Part of our work was understanding that existing system\u2014its logic, constraints, and user feedback\u2014and evolving it rather than starting from a blank canvas. The redesign had to respect what already worked while making the structure clearer, more scalable, and easier to navigate.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A heavy iteration loop formed between design and engineering. Much of the logic revolved around what the team called \u201cdegree days\u201d\u2014a thermal accumulation model used to predict insect development and activity. Pest thresholds were decision triggers tied to these heat-based growth cycles. In parallel, the system also needed to reflect crop growth stages, since certain phases of plant development can directly influence insect behavior and treatment timing. The engineer would explain how these models interacted\u2014heat accumulation, insect lifecycle stages, crop growth phases. We\u2019d prototype how that logic surfaces in the interface. He\u2019d point out an edge case. We\u2019d refine. This loop repeated until the structure made sense both scientifically and operationally.<\/span><\/p>\n<p><iframe loading=\"lazy\" title=\"3\" src=\"https:\/\/player.vimeo.com\/video\/1086309828?dnt=1&amp;app_id=122963\" width=\"500\" height=\"370\" frameborder=\"0\" allow=\"autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\"><\/iframe><\/p>\n<h3><strong>Design Takeaways<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">One insight shaped much of the UI: insects develop faster with more heat. That biological fact became a design driver.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Users needed to see thermal accumulation clearly. More importantly, they needed to sense urgency before an outbreak threshold was reached. We designed visual cues that escalate\u2014not in dramatic red banners, but in calibrated signals that build tension as risk increases.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">It\u2019s similar to how you notice your car\u2019s fuel gauge dipping long before the tank is empty. The goal wasn\u2019t panic, it was awareness.<\/span><\/p>\n<h2><strong>UX &amp; User Flows<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">We built detailed user flows for critical actions. Managing devices meant handling multiple states: assigning to organizations, marking as broken, sending for repair, decommissioning. Each transition had consequences. The flow had to be predictable.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Creating and visualizing field entities required spatial clarity. Users needed to understand which sensors belonged to which fields and how that tied to crop vulnerability.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Tracking insect activity meant surfacing alerts that were actionable. Not abstract graphs. Decisions.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The UX phase involved multiple iteration rounds. Stakeholders brought different perspectives: engineering feasibility, agronomic accuracy, operational clarity. Each review sharpened the system.<\/span><\/p>\n<h3><strong>UX Focus<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">We kept returning to three principles:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Make complex data simple to act on.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Define clear paths for both novice and experienced users.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Maintain clarity under high information density.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">High-density dashboards fail when hierarchy collapses. We used modular components, consistent spacing tokens, and restrained typography scales to keep the interface breathable. The goal wasn\u2019t minimalism. It was legibility under stress.<\/span><\/p>\n<p><iframe loading=\"lazy\" title=\"1\" src=\"https:\/\/player.vimeo.com\/video\/1086309918?dnt=1&amp;app_id=122963\" width=\"500\" height=\"333\" frameborder=\"0\" allow=\"autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\"><\/iframe><\/p>\n<h2><strong>UI Concept &amp; Visual Design<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">All architecture, wireframes, and UI workflows were executed in Figma. Not as a static canvas, but as a system.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">We defined components and states early. Cards for fields. Badges for device status. Alert modules that could scale in intensity without breaking layout. Design tokens controlled color, spacing, and typography so escalation states remained consistent across screens.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The dashboard screens were intentionally data-dense, but structured. Visual <a href=\"https:\/\/blog.tubikstudio.com\/9-effective-tips-on-visual-hierarchy?utm_source=blog&amp;utm_medium=referral&amp;utm_campaign=internal_traffic&amp;utm_content=farmsense_case_study&amp;source=blog\">hierarchy<\/a> did the heavy lifting: primary metrics surfaced first, secondary context nested below. No decorative gradients competing with numbers that matter.<\/span><\/p>\n<h2><strong>Admin Panel &amp; Interaction Design<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">The admin dashboard managed interconnected entities.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Organizations had separate administrator lists. Devices existed in multiple states: available in a general pool, assigned to organizations, broken and sent for repair, decommissioned for disposal. Insects and crops had dedicated management lists with clear add, edit, and delete actions. Profiles applied specific configurations to insect data.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The UX intent was to unite all entities into a single coherent system. Relationships had to be visible. If a device changed state, its implications needed to ripple logically through the interface.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Hierarchy became our discipline. Clean structure over clever visuals. Clear affordances over experimentation.<\/span><\/p>\n<p><iframe loading=\"lazy\" title=\"4\" src=\"https:\/\/player.vimeo.com\/video\/1086309959?dnt=1&amp;app_id=122963\" width=\"500\" height=\"321\" frameborder=\"0\" allow=\"autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\"><\/iframe><\/p>\n<h2><strong>Cross-Platform Considerations<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">FarmSense operates in agricultural environments. That means users might access data from a desktop in an office or from a mobile device in the field.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">We designed responsive behaviors that prioritize <a href=\"https:\/\/blog.tubikstudio.com\/ux-design-readable-user-interface?utm_source=blog&amp;utm_medium=referral&amp;utm_campaign=internal_traffic&amp;utm_content=farmsense_case_study&amp;source=blog\">readability<\/a> and essential actions. On smaller screens, secondary data compresses gracefully. Core alerts remain prominent. Interaction targets remain generous enough for real-world conditions\u2014not lab-perfect cursor precision.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Context matters. We designed for it.<\/span><\/p>\n<p><iframe loading=\"lazy\" title=\"5\" src=\"https:\/\/player.vimeo.com\/video\/1086309882?dnt=1&amp;app_id=122963\" width=\"500\" height=\"344\" frameborder=\"0\" allow=\"autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\"><\/iframe><\/p>\n<h2><strong>Final Reflections<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">FarmSense was ultimately a translation challenge. We took scientific, entomological, and sensor-driven complexity and structured it into workflows that feel usable in real agricultural contexts.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">What we learned along the way is, complexity isn\u2019t the enemy. Ambiguity is. Growers are not afraid of data. They live inside uncertainty every season\u2014weather shifts, market pressure, biological variability. What they need is structure that respects their expertise while reducing cognitive friction. A well-designed system doesn\u2019t simplify reality, it doesn\u2019t dumb things down; it makes cause and effect visible.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">We also learned that urgency is a design material. Thermal days accumulating over time are not dramatic in themselves. But when tied to pest thresholds, they carry tension. The interface had to express that escalation without theatrics.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Design, at its best, makes expertise usable. In FarmSense, agricultural data stopped being abstract telemetry and became operational clarity.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">And that shift\u2014from data to decision\u2014is where product design proves its worth.<\/span><\/p>\n<h2 data-start=\"2416\" data-end=\"2437\">Recommended Reading<\/h2>\n<p data-start=\"2439\" data-end=\"2491\">If you enjoyed this case study, you might also like:<\/p>\n<p data-start=\"2439\" data-end=\"2491\"><a href=\"https:\/\/blog.tubikstudio.com\/fireside-healthcare-web-design-case-study?utm_source=blog&amp;utm_medium=referral&amp;utm_campaign=internal_traffic&amp;utm_content=farmsense_case_study&amp;source=blog\">Fireside Case Study: Turning Sterile into Human<\/a><\/p>\n<p data-start=\"2439\" data-end=\"2491\"><a href=\"https:\/\/blog.tubikstudio.com\/orakle-medical-education-web-design?utm_source=blog&amp;utm_medium=referral&amp;utm_campaign=internal_traffic&amp;utm_content=farmsense_case_study&amp;source=blog\">Case Study: Orakle. Modern Web Design for Medical Education<\/a><\/p>\n<p data-start=\"2439\" data-end=\"2491\"><a href=\"https:\/\/blog.tubikstudio.com\/case-study-abuk-designing-ukraines-leading-audiobook-platform?utm_source=blog&amp;utm_medium=referral&amp;utm_campaign=internal_traffic&amp;utm_content=farmsense_case_study&amp;source=blog\">Case Study: ABUK\u2014Designing Ukraine\u2019s Leading Audiobook Platform<\/a><\/p>\n<p data-start=\"2439\" data-end=\"2491\"><a href=\"https:\/\/blog.tubikstudio.com\/eterna-cloud-case-study?utm_source=blog&amp;utm_medium=referral&amp;utm_campaign=internal_traffic&amp;utm_content=farmsense_case_study&amp;source=blog\">EternaCloud Case Study: Calm Design for Complex Systems<\/a><\/p>\n<p data-start=\"2439\" data-end=\"2491\"><a href=\"https:\/\/blog.tubikstudio.com\/spylt-case-study?utm_source=blog&amp;utm_medium=referral&amp;utm_campaign=internal_traffic&amp;utm_content=farmsense_case_study&amp;source=blog\">SPYLT Case Study: Delicious by Design<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>How entomology models, sensor telemetry, and agricultural workflows shaped a dashboard that helps growers understand risk early\u2014and act before crop loss becomes visible.<\/p>\n","protected":false},"author":10003,"featured_media":17416,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[4,9],"tags":[683,684,685,686,687,688,689,57,108,440,447,457,502,503,504,682],"coauthors":[634],"class_list":["post-17229","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-case_study","category-ui_ux","tag-dashboard-design","tag-ux-case-study","tag-data-visualization","tag-agricultural-software","tag-sensor-data","tag-product-design-process","tag-enterprise-ux","tag-case-study","tag-design-case-study","tag-tubik","tag-tubik-studio","tag-ui","tag-ux","tag-ux-design","tag-ux-design-article","tag-agtech"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v25.7 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>FarmSense Case Study: Fields, Sensors, and System Thinking<\/title>\n<meta name=\"description\" content=\"How we translated entomology, sensor telemetry, and agricultural data into a clear UX system that helps growers detect pest threats early.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/tubikstudio.com\/blog\/farmsense-case-study\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"FarmSense Case Study: Fields, Sensors, and System Thinking\" \/>\n<meta property=\"og:description\" content=\"How we translated entomology, sensor telemetry, and agricultural data into a clear UX system that helps growers detect pest threats early.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/tubikstudio.com\/blog\/farmsense-case-study\/\" \/>\n<meta property=\"og:site_name\" content=\"Tubik Blog: Articles About Design\" \/>\n<meta property=\"article:published_time\" content=\"2026-03-05T14:41:05+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-04-06T12:24:20+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.tubikstudio.com\/wp-content\/uploads\/2026\/03\/tubik_design_studio_FarmSense-case-study-1.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"600\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Anastasiia Lutsenko\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Anastasiia Lutsenko\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/tubikstudio.com\/blog\/farmsense-case-study\/\",\"url\":\"https:\/\/tubikstudio.com\/blog\/farmsense-case-study\/\",\"name\":\"FarmSense Case Study: Fields, Sensors, and System Thinking\",\"isPartOf\":{\"@id\":\"https:\/\/tubikstudio.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/tubikstudio.com\/blog\/farmsense-case-study\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/tubikstudio.com\/blog\/farmsense-case-study\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/blog.tubikstudio.com\/wp-content\/uploads\/2026\/03\/tubik_design_studio_FarmSense-case-study-1.png\",\"datePublished\":\"2026-03-05T14:41:05+00:00\",\"dateModified\":\"2026-04-06T12:24:20+00:00\",\"author\":{\"@id\":\"https:\/\/tubikstudio.com\/blog\/#\/schema\/person\/2d8ccd57b6edf253e2787561fe1e66c1\"},\"description\":\"How we translated entomology, sensor telemetry, and agricultural data into a clear UX system that helps growers detect pest threats early.\",\"breadcrumb\":{\"@id\":\"https:\/\/tubikstudio.com\/blog\/farmsense-case-study\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/tubikstudio.com\/blog\/farmsense-case-study\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/tubikstudio.com\/blog\/farmsense-case-study\/#primaryimage\",\"url\":\"https:\/\/blog.tubikstudio.com\/wp-content\/uploads\/2026\/03\/tubik_design_studio_FarmSense-case-study-1.png\",\"contentUrl\":\"https:\/\/blog.tubikstudio.com\/wp-content\/uploads\/2026\/03\/tubik_design_studio_FarmSense-case-study-1.png\",\"width\":1200,\"height\":600},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/tubikstudio.com\/blog\/farmsense-case-study\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/tubikstudio.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"FarmSense Case Study: Fields, Sensors, and System Thinking\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/tubikstudio.com\/blog\/#website\",\"url\":\"https:\/\/tubikstudio.com\/blog\/\",\"name\":\"Tubik Blog: Articles About Design\",\"description\":\"Tubik Studio\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/tubikstudio.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/tubikstudio.com\/blog\/#\/schema\/person\/2d8ccd57b6edf253e2787561fe1e66c1\",\"name\":\"Anastasiia Lutsenko\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/tubikstudio.com\/blog\/#\/schema\/person\/image\/d893c1e4578c8cd7a39f393978129a25\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/9c0999380ab25553a4aea6cbc2224fa5f579af8ebbef2928d1d71fd4137a77a1?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/9c0999380ab25553a4aea6cbc2224fa5f579af8ebbef2928d1d71fd4137a77a1?s=96&d=mm&r=g\",\"caption\":\"Anastasiia Lutsenko\"},\"description\":\"7+ years of writing content that speaks, sells, and sticks. Raised on legendary Apple commercials and allergic to mediocrity, Anastasiia writes for products, interfaces, and campaigns that refuse to be ignored.\",\"url\":\"https:\/\/tubikstudio.com\/blog\/author\/alutsenko\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"FarmSense Case Study: Fields, Sensors, and System Thinking","description":"How we translated entomology, sensor telemetry, and agricultural data into a clear UX system that helps growers detect pest threats early.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/tubikstudio.com\/blog\/farmsense-case-study\/","og_locale":"en_US","og_type":"article","og_title":"FarmSense Case Study: Fields, Sensors, and System Thinking","og_description":"How we translated entomology, sensor telemetry, and agricultural data into a clear UX system that helps growers detect pest threats early.","og_url":"https:\/\/tubikstudio.com\/blog\/farmsense-case-study\/","og_site_name":"Tubik Blog: Articles About Design","article_published_time":"2026-03-05T14:41:05+00:00","article_modified_time":"2026-04-06T12:24:20+00:00","og_image":[{"width":1200,"height":600,"url":"https:\/\/blog.tubikstudio.com\/wp-content\/uploads\/2026\/03\/tubik_design_studio_FarmSense-case-study-1.png","type":"image\/png"}],"author":"Anastasiia Lutsenko","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Anastasiia Lutsenko","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/tubikstudio.com\/blog\/farmsense-case-study\/","url":"https:\/\/tubikstudio.com\/blog\/farmsense-case-study\/","name":"FarmSense Case Study: Fields, Sensors, and System Thinking","isPartOf":{"@id":"https:\/\/tubikstudio.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/tubikstudio.com\/blog\/farmsense-case-study\/#primaryimage"},"image":{"@id":"https:\/\/tubikstudio.com\/blog\/farmsense-case-study\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.tubikstudio.com\/wp-content\/uploads\/2026\/03\/tubik_design_studio_FarmSense-case-study-1.png","datePublished":"2026-03-05T14:41:05+00:00","dateModified":"2026-04-06T12:24:20+00:00","author":{"@id":"https:\/\/tubikstudio.com\/blog\/#\/schema\/person\/2d8ccd57b6edf253e2787561fe1e66c1"},"description":"How we translated entomology, sensor telemetry, and agricultural data into a clear UX system that helps growers detect pest threats early.","breadcrumb":{"@id":"https:\/\/tubikstudio.com\/blog\/farmsense-case-study\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/tubikstudio.com\/blog\/farmsense-case-study\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/tubikstudio.com\/blog\/farmsense-case-study\/#primaryimage","url":"https:\/\/blog.tubikstudio.com\/wp-content\/uploads\/2026\/03\/tubik_design_studio_FarmSense-case-study-1.png","contentUrl":"https:\/\/blog.tubikstudio.com\/wp-content\/uploads\/2026\/03\/tubik_design_studio_FarmSense-case-study-1.png","width":1200,"height":600},{"@type":"BreadcrumbList","@id":"https:\/\/tubikstudio.com\/blog\/farmsense-case-study\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/tubikstudio.com\/blog\/"},{"@type":"ListItem","position":2,"name":"FarmSense Case Study: Fields, Sensors, and System Thinking"}]},{"@type":"WebSite","@id":"https:\/\/tubikstudio.com\/blog\/#website","url":"https:\/\/tubikstudio.com\/blog\/","name":"Tubik Blog: Articles About Design","description":"Tubik Studio","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/tubikstudio.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/tubikstudio.com\/blog\/#\/schema\/person\/2d8ccd57b6edf253e2787561fe1e66c1","name":"Anastasiia Lutsenko","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/tubikstudio.com\/blog\/#\/schema\/person\/image\/d893c1e4578c8cd7a39f393978129a25","url":"https:\/\/secure.gravatar.com\/avatar\/9c0999380ab25553a4aea6cbc2224fa5f579af8ebbef2928d1d71fd4137a77a1?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/9c0999380ab25553a4aea6cbc2224fa5f579af8ebbef2928d1d71fd4137a77a1?s=96&d=mm&r=g","caption":"Anastasiia Lutsenko"},"description":"7+ years of writing content that speaks, sells, and sticks. Raised on legendary Apple commercials and allergic to mediocrity, Anastasiia writes for products, interfaces, and campaigns that refuse to be ignored.","url":"https:\/\/tubikstudio.com\/blog\/author\/alutsenko\/"}]}},"post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/tubikstudio.com\/blog\/wp-json\/wp\/v2\/posts\/17229","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tubikstudio.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tubikstudio.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tubikstudio.com\/blog\/wp-json\/wp\/v2\/users\/10003"}],"replies":[{"embeddable":true,"href":"https:\/\/tubikstudio.com\/blog\/wp-json\/wp\/v2\/comments?post=17229"}],"version-history":[{"count":4,"href":"https:\/\/tubikstudio.com\/blog\/wp-json\/wp\/v2\/posts\/17229\/revisions"}],"predecessor-version":[{"id":17235,"href":"https:\/\/tubikstudio.com\/blog\/wp-json\/wp\/v2\/posts\/17229\/revisions\/17235"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/tubikstudio.com\/blog\/wp-json\/wp\/v2\/media\/17416"}],"wp:attachment":[{"href":"https:\/\/tubikstudio.com\/blog\/wp-json\/wp\/v2\/media?parent=17229"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tubikstudio.com\/blog\/wp-json\/wp\/v2\/categories?post=17229"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tubikstudio.com\/blog\/wp-json\/wp\/v2\/tags?post=17229"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/tubikstudio.com\/blog\/wp-json\/wp\/v2\/coauthors?post=17229"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}