{"id":889,"date":"2026-02-09T06:14:00","date_gmt":"2026-02-09T06:14:00","guid":{"rendered":"https:\/\/graph.co.ke\/blog\/?p=889"},"modified":"2026-02-09T06:14:13","modified_gmt":"2026-02-09T06:14:13","slug":"why-most-software-requirements-documents-are-useless","status":"publish","type":"post","link":"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/","title":{"rendered":"Why Most Software Requirements Documents Are Useless"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\"><\/h2>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/makingofsoftware.com\/docs\/Software_Product_Specification_200402_1.png\" alt=\"https:\/\/makingofsoftware.com\/docs\/Software_Product_Specification_200402_1.png\"\/><\/figure>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/www.researchgate.net\/publication\/353274366\/figure\/fig3\/AS%3A1058181090381826%401629301440605\/Ambiguity-detection-flow-chart.ppm\" alt=\"https:\/\/www.researchgate.net\/publication\/353274366\/figure\/fig3\/AS%3A1058181090381826%401629301440605\/Ambiguity-detection-flow-chart.ppm\"\/><\/figure>\n\n\n\n<p>Most software projects do not fail because of poor engineering.<br>They fail because they start with documents that describe <em>what people want<\/em> instead of <em>what systems must survive<\/em>.<\/p>\n\n\n\n<p>In Kenya, requirements documents are often treated as a contractual formality rather than a thinking tool. The result is predictable misalignment, endless change requests, and systems that technically meet requirements but fail operationally.<\/p>\n\n\n\n<p>This article explains <strong>why most requirements documents are useless<\/strong>, and what should replace them.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">1. Requirements Describe Wishes, Not Constraints<\/h2>\n\n\n\n<p>Typical requirements documents focus on:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Features<\/li>\n\n\n\n<li>Screens<\/li>\n\n\n\n<li>User flows<\/li>\n\n\n\n<li>Permissions<\/li>\n<\/ul>\n\n\n\n<p>They rarely define:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Failure conditions<\/li>\n\n\n\n<li>Load expectations<\/li>\n\n\n\n<li>Data ownership<\/li>\n\n\n\n<li>Regulatory exposure<\/li>\n\n\n\n<li>Long-term maintenance assumptions<\/li>\n<\/ul>\n\n\n\n<p>Systems do not fail because features are missing.<br>They fail because constraints were never articulated.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">2. Ambiguity Is Mistaken for Flexibility<\/h2>\n\n\n\n<p>Vague requirements are often defended as \u201cflexibility.\u201d<\/p>\n\n\n\n<p>In reality, ambiguity:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Pushes decisions downstream<\/li>\n\n\n\n<li>Transfers risk to engineering<\/li>\n\n\n\n<li>Creates false alignment<\/li>\n\n\n\n<li>Explodes cost later<\/li>\n<\/ul>\n\n\n\n<p>Every unclear requirement is a delayed decision that someone else will pay for.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">3. Requirements Ignore Time<\/h2>\n\n\n\n<p>Most documents assume the system exists at a single moment.<\/p>\n\n\n\n<p>They do not describe:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>How the system evolves<\/li>\n\n\n\n<li>What happens when data doubles<\/li>\n\n\n\n<li>How regulations change<\/li>\n\n\n\n<li>What breaks first under stress<\/li>\n<\/ul>\n\n\n\n<p>Software lives in time.<br>Requirements that ignore time are incomplete.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">4. What Works Better Than Traditional Requirements<\/h2>\n\n\n\n<p>Successful teams replace rigid requirement documents with:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Problem statements<\/li>\n\n\n\n<li>Decision maps<\/li>\n\n\n\n<li>Constraints lists<\/li>\n\n\n\n<li>Failure-mode discussions<\/li>\n\n\n\n<li>Ownership definitions<\/li>\n<\/ul>\n\n\n\n<p>The goal is not completeness.<br>It is shared understanding of reality.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Final Thought<\/h2>\n\n\n\n<p>Good software is not built from exhaustive requirements.<br>It is built from <strong>clear constraints, explicit trade-offs, and disciplined thinking<\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Most software projects do not fail because of poor engineering.They fail because they start with documents that describe what people want instead of what systems must survive. In Kenya, requirements documents are often treated as a contractual formality rather than a thinking tool. The result is predictable misalignment, endless change requests, and systems that technically meet requirements but fail operationally. This article explains why most requirements documents are useless, and what should replace them. 1. Requirements Describe Wishes, Not Constraints Typical requirements documents focus on: They rarely define: Systems do not fail because features are missing.They fail because constraints were never articulated. 2. Ambiguity Is Mistaken for Flexibility Vague requirements are often defended as \u201cflexibility.\u201d In reality, ambiguity: Every unclear requirement is a delayed decision that someone else will pay for. 3. Requirements Ignore Time Most documents assume the system exists at a single moment. They do not describe: Software lives in time.Requirements that ignore time are incomplete. 4. What Works Better Than Traditional Requirements Successful teams replace rigid requirement documents with: The goal is not completeness.It is shared understanding of reality. Final Thought Good software is not built from exhaustive requirements.It is built from clear constraints, explicit trade-offs, and disciplined thinking.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"categories":[47,16,18],"tags":[22,19,26],"class_list":["post-889","post","type-post","status-publish","format-standard","hentry","category-ai-solutions","category-how-kenya-is-doing-in-technoloy","category-top-web-developers-in-lenya","tag-app-development","tag-mobile-development-kenya","tag-web_development_kenya"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.7 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Why Most Software Requirements Documents Are Useless - Graph Technologies<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Why Most Software Requirements Documents Are Useless - Graph Technologies\" \/>\n<meta property=\"og:description\" content=\"Most software projects do not fail because of poor engineering.They fail because they start with documents that describe what people want instead of what systems must survive. In Kenya, requirements documents are often treated as a contractual formality rather than a thinking tool. The result is predictable misalignment, endless change requests, and systems that technically meet requirements but fail operationally. This article explains why most requirements documents are useless, and what should replace them. 1. Requirements Describe Wishes, Not Constraints Typical requirements documents focus on: They rarely define: Systems do not fail because features are missing.They fail because constraints were never articulated. 2. Ambiguity Is Mistaken for Flexibility Vague requirements are often defended as \u201cflexibility.\u201d In reality, ambiguity: Every unclear requirement is a delayed decision that someone else will pay for. 3. Requirements Ignore Time Most documents assume the system exists at a single moment. They do not describe: Software lives in time.Requirements that ignore time are incomplete. 4. What Works Better Than Traditional Requirements Successful teams replace rigid requirement documents with: The goal is not completeness.It is shared understanding of reality. Final Thought Good software is not built from exhaustive requirements.It is built from clear constraints, explicit trade-offs, and disciplined thinking.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/\" \/>\n<meta property=\"og:site_name\" content=\"Graph Technologies\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/graphAfrica\/\" \/>\n<meta property=\"article:published_time\" content=\"2026-02-09T06:14:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-02-09T06:14:13+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/makingofsoftware.com\/docs\/Software_Product_Specification_200402_1.png\" \/>\n<meta name=\"author\" content=\"GraphAdmin\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"GraphAdmin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"2 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/\"},\"author\":{\"name\":\"GraphAdmin\",\"@id\":\"https:\/\/graph.co.ke\/blog\/#\/schema\/person\/dd09a2ef67b9cd1edf706e168a2f914a\"},\"headline\":\"Why Most Software Requirements Documents Are Useless\",\"datePublished\":\"2026-02-09T06:14:00+00:00\",\"dateModified\":\"2026-02-09T06:14:13+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/\"},\"wordCount\":266,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/graph.co.ke\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/makingofsoftware.com\/docs\/Software_Product_Specification_200402_1.png\",\"keywords\":[\"app-development\",\"mobile-development-kenya\",\"web_development_kenya\"],\"articleSection\":[\"AI Solutions\",\"Technology\",\"Web Development\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/\",\"url\":\"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/\",\"name\":\"Why Most Software Requirements Documents Are Useless - Graph Technologies\",\"isPartOf\":{\"@id\":\"https:\/\/graph.co.ke\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/makingofsoftware.com\/docs\/Software_Product_Specification_200402_1.png\",\"datePublished\":\"2026-02-09T06:14:00+00:00\",\"dateModified\":\"2026-02-09T06:14:13+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/#primaryimage\",\"url\":\"https:\/\/makingofsoftware.com\/docs\/Software_Product_Specification_200402_1.png\",\"contentUrl\":\"https:\/\/makingofsoftware.com\/docs\/Software_Product_Specification_200402_1.png\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/graph.co.ke\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Why Most Software Requirements Documents Are Useless\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/graph.co.ke\/blog\/#website\",\"url\":\"https:\/\/graph.co.ke\/blog\/\",\"name\":\"Graph Technologies\",\"description\":\"Graph Technologies\",\"publisher\":{\"@id\":\"https:\/\/graph.co.ke\/blog\/#organization\"},\"alternateName\":\"Graph Africa\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/graph.co.ke\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/graph.co.ke\/blog\/#organization\",\"name\":\"GraphTechnologies\",\"alternateName\":\"Graph Africa\",\"url\":\"https:\/\/graph.co.ke\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/graph.co.ke\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/graph.co.ke\/blog\/wp-content\/uploads\/2018\/09\/graph_logo.png\",\"contentUrl\":\"https:\/\/graph.co.ke\/blog\/wp-content\/uploads\/2018\/09\/graph_logo.png\",\"width\":512,\"height\":512,\"caption\":\"GraphTechnologies\"},\"image\":{\"@id\":\"https:\/\/graph.co.ke\/blog\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/graphAfrica\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/graph.co.ke\/blog\/#\/schema\/person\/dd09a2ef67b9cd1edf706e168a2f914a\",\"name\":\"GraphAdmin\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/graph.co.ke\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/9a97384175f57b83bfbbcec6cb2fc94346ce6f91d57dffce1b61e699e42d924d?s=96&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/9a97384175f57b83bfbbcec6cb2fc94346ce6f91d57dffce1b61e699e42d924d?s=96&r=g\",\"caption\":\"GraphAdmin\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Why Most Software Requirements Documents Are Useless - Graph Technologies","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:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/","og_locale":"en_US","og_type":"article","og_title":"Why Most Software Requirements Documents Are Useless - Graph Technologies","og_description":"Most software projects do not fail because of poor engineering.They fail because they start with documents that describe what people want instead of what systems must survive. In Kenya, requirements documents are often treated as a contractual formality rather than a thinking tool. The result is predictable misalignment, endless change requests, and systems that technically meet requirements but fail operationally. This article explains why most requirements documents are useless, and what should replace them. 1. Requirements Describe Wishes, Not Constraints Typical requirements documents focus on: They rarely define: Systems do not fail because features are missing.They fail because constraints were never articulated. 2. Ambiguity Is Mistaken for Flexibility Vague requirements are often defended as \u201cflexibility.\u201d In reality, ambiguity: Every unclear requirement is a delayed decision that someone else will pay for. 3. Requirements Ignore Time Most documents assume the system exists at a single moment. They do not describe: Software lives in time.Requirements that ignore time are incomplete. 4. What Works Better Than Traditional Requirements Successful teams replace rigid requirement documents with: The goal is not completeness.It is shared understanding of reality. Final Thought Good software is not built from exhaustive requirements.It is built from clear constraints, explicit trade-offs, and disciplined thinking.","og_url":"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/","og_site_name":"Graph Technologies","article_publisher":"https:\/\/www.facebook.com\/graphAfrica\/","article_published_time":"2026-02-09T06:14:00+00:00","article_modified_time":"2026-02-09T06:14:13+00:00","og_image":[{"url":"https:\/\/makingofsoftware.com\/docs\/Software_Product_Specification_200402_1.png","type":"","width":"","height":""}],"author":"GraphAdmin","twitter_card":"summary_large_image","twitter_misc":{"Written by":"GraphAdmin","Est. reading time":"2 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/#article","isPartOf":{"@id":"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/"},"author":{"name":"GraphAdmin","@id":"https:\/\/graph.co.ke\/blog\/#\/schema\/person\/dd09a2ef67b9cd1edf706e168a2f914a"},"headline":"Why Most Software Requirements Documents Are Useless","datePublished":"2026-02-09T06:14:00+00:00","dateModified":"2026-02-09T06:14:13+00:00","mainEntityOfPage":{"@id":"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/"},"wordCount":266,"commentCount":0,"publisher":{"@id":"https:\/\/graph.co.ke\/blog\/#organization"},"image":{"@id":"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/#primaryimage"},"thumbnailUrl":"https:\/\/makingofsoftware.com\/docs\/Software_Product_Specification_200402_1.png","keywords":["app-development","mobile-development-kenya","web_development_kenya"],"articleSection":["AI Solutions","Technology","Web Development"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/","url":"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/","name":"Why Most Software Requirements Documents Are Useless - Graph Technologies","isPartOf":{"@id":"https:\/\/graph.co.ke\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/#primaryimage"},"image":{"@id":"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/#primaryimage"},"thumbnailUrl":"https:\/\/makingofsoftware.com\/docs\/Software_Product_Specification_200402_1.png","datePublished":"2026-02-09T06:14:00+00:00","dateModified":"2026-02-09T06:14:13+00:00","breadcrumb":{"@id":"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/#primaryimage","url":"https:\/\/makingofsoftware.com\/docs\/Software_Product_Specification_200402_1.png","contentUrl":"https:\/\/makingofsoftware.com\/docs\/Software_Product_Specification_200402_1.png"},{"@type":"BreadcrumbList","@id":"https:\/\/graph.co.ke\/blog\/2026\/02\/09\/why-most-software-requirements-documents-are-useless\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/graph.co.ke\/blog\/"},{"@type":"ListItem","position":2,"name":"Why Most Software Requirements Documents Are Useless"}]},{"@type":"WebSite","@id":"https:\/\/graph.co.ke\/blog\/#website","url":"https:\/\/graph.co.ke\/blog\/","name":"Graph Technologies","description":"Graph Technologies","publisher":{"@id":"https:\/\/graph.co.ke\/blog\/#organization"},"alternateName":"Graph Africa","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/graph.co.ke\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/graph.co.ke\/blog\/#organization","name":"GraphTechnologies","alternateName":"Graph Africa","url":"https:\/\/graph.co.ke\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/graph.co.ke\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/graph.co.ke\/blog\/wp-content\/uploads\/2018\/09\/graph_logo.png","contentUrl":"https:\/\/graph.co.ke\/blog\/wp-content\/uploads\/2018\/09\/graph_logo.png","width":512,"height":512,"caption":"GraphTechnologies"},"image":{"@id":"https:\/\/graph.co.ke\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/graphAfrica\/"]},{"@type":"Person","@id":"https:\/\/graph.co.ke\/blog\/#\/schema\/person\/dd09a2ef67b9cd1edf706e168a2f914a","name":"GraphAdmin","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/graph.co.ke\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/9a97384175f57b83bfbbcec6cb2fc94346ce6f91d57dffce1b61e699e42d924d?s=96&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/9a97384175f57b83bfbbcec6cb2fc94346ce6f91d57dffce1b61e699e42d924d?s=96&r=g","caption":"GraphAdmin"}}]}},"_links":{"self":[{"href":"https:\/\/graph.co.ke\/blog\/wp-json\/wp\/v2\/posts\/889","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/graph.co.ke\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/graph.co.ke\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/graph.co.ke\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/graph.co.ke\/blog\/wp-json\/wp\/v2\/comments?post=889"}],"version-history":[{"count":1,"href":"https:\/\/graph.co.ke\/blog\/wp-json\/wp\/v2\/posts\/889\/revisions"}],"predecessor-version":[{"id":890,"href":"https:\/\/graph.co.ke\/blog\/wp-json\/wp\/v2\/posts\/889\/revisions\/890"}],"wp:attachment":[{"href":"https:\/\/graph.co.ke\/blog\/wp-json\/wp\/v2\/media?parent=889"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/graph.co.ke\/blog\/wp-json\/wp\/v2\/categories?post=889"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/graph.co.ke\/blog\/wp-json\/wp\/v2\/tags?post=889"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}