{"docs":[{"id":5,"title":"Pre-Project Preparation: The Foundation for Better Electronics and Software","heading":"Pre-Project Preparation: The Foundation for Better Electronics and Software","subheading":null,"category":"Project Discovery","body":null,"tags":"Project Discovery, Technical Specification, Product Strategy","cardCta":{"label":null,"link":null},"pageCta":{"label":"Talk to AAVICO engineering","link":"/contact"},"excerpt":"The cheapest time to change a product is before anyone has drawn a schematic. A short discovery phase is how you use that time.","featuredImage":{"id":123,"alt":"Pre-Project Preparation: The Foundation for Better Electronics and Software","isPrivate":false,"updatedAt":"2026-10-12T20:16:27.230Z","createdAt":"2026-10-12T20:16:27.230Z","url":"/api/media/file/pre-project-preparation-foundation.png","thumbnailURL":null,"filename":"pre-project-preparation-foundation.png","mimeType":"image/png","filesize":1937213,"width":2400,"height":1360,"focalX":null,"focalY":null,"sizes":{"thumbnail":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null},"card":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null}}},"type":"Blog","readTime":"3 min read","publishedAt":"2025-10-31T00:00:00.000Z","heroImage":{"id":123,"alt":"Pre-Project Preparation: The Foundation for Better Electronics and Software","isPrivate":false,"updatedAt":"2026-10-12T20:16:27.230Z","createdAt":"2026-10-12T20:16:27.230Z","url":"/api/media/file/pre-project-preparation-foundation.png","thumbnailURL":null,"filename":"pre-project-preparation-foundation.png","mimeType":"image/png","filesize":1937213,"width":2400,"height":1360,"focalX":null,"focalY":null,"sizes":{"thumbnail":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null},"card":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null}}},"introText":"Most overruns in electronics and software projects trace back to decisions that were never actually made: who the product is for, what it must do on day one, and what it is allowed to cost. A discovery phase forces those decisions early, while changing your mind costs a conversation rather than a board respin. This article sets out what that phase should produce and how to tell when it has done its job.","metrics":[{"id":"pre-project-preparation-the-foundation-f-metric-1","value":"Scope","label":"A written list of what the first release must do, and what it deliberately leaves out.","icon":null},{"id":"pre-project-preparation-the-foundation-f-metric-2","value":"Feasibility","label":"The riskiest technical assumptions tested with small experiments before the design depends on them.","icon":null},{"id":"pre-project-preparation-the-foundation-f-metric-3","value":"Estimate","label":"Effort and cost given as a range, with the assumptions behind each end stated.","icon":null},{"id":"pre-project-preparation-the-foundation-f-metric-4","value":"Risk register","label":"Known unknowns ranked by impact, each with an owner and a next step.","icon":null}],"gallery":[],"challenge":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"Early conversations about a product are full of agreement that turns out to be shallow. Two people can say “low power” and mean a week on a coin cell or a day on a phone battery. Until requirements are written down and challenged, every estimate is a guess about a different product.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"The work at this stage is to replace assumptions with decisions: define the user and the use case, separate requirements from wishes, check that the hard parts are physically and commercially possible, and say plainly what is still unknown.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"blockquote":{"quote":"An estimate is only as good as the requirements behind it. Discovery is where you find out which requirements you actually have.","author":null,"role":"AAVICO Engineering"},"supportImage1":null,"deliverables":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"A product brief: target users, the problem being solved, the competing options and the constraints that cannot move, such as unit cost, size, battery life or a launch date.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"A technical specification covering functional and non-functional requirements, candidate architectures and key components, and any certification the target market requires.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"A feasibility summary, an estimate expressed as a range, and a risk list, so the decision to proceed is made with the uncertainty visible.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"results":[{"id":"pre-project-preparation-the-foundation-f-result-1","title":"Planning Impact","description":"Everyone works from one description of the product, so later disagreements are about trade-offs rather than about what was meant."},{"id":"pre-project-preparation-the-foundation-f-result-2","title":"Engineering Impact","description":"Architecture and component choices are made against stated requirements and can be defended when they are questioned."},{"id":"pre-project-preparation-the-foundation-f-result-3","title":"Commercial Impact","description":"Budget and schedule are discussed as ranges with reasons, which makes them easier to plan around and to revisit."},{"id":"pre-project-preparation-the-foundation-f-result-4","title":"Risk Impact","description":"Problems that would have appeared during prototyping are found when the only thing to change is a document."}],"lookingAhead":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"A good discovery package converts directly into a plan: an architecture, milestones with acceptance criteria, and a first prototype aimed at the largest remaining risk.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"The same approach works for a product that already exists. Reviewing a prototype or a fielded design against its real requirements shows what to keep, what to redesign and in what order.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"supportImage2":null,"testimonial":{"quote":null,"author":null,"role":null,"photo":null},"challengesSolved":[{"id":"pre-project-preparation-the-foundation-f-challenge-1","title":"Requirements that mean different things to different people","description":null,"icon":null},{"id":"pre-project-preparation-the-foundation-f-challenge-2","title":"Technical assumptions nobody has tested","description":null,"icon":null},{"id":"pre-project-preparation-the-foundation-f-challenge-3","title":"Estimates given without stated assumptions","description":null,"icon":null},{"id":"pre-project-preparation-the-foundation-f-challenge-4","title":"Risks discovered only after the design is committed","description":null,"icon":null}],"relatedPosts":[],"contactUs":{"show":true},"updatedAt":"2026-10-14T04:40:04.074Z","createdAt":"2026-09-25T14:52:47.759Z"}],"hasNextPage":false,"hasPrevPage":false,"limit":10,"nextPage":null,"page":1,"pagingCounter":1,"prevPage":null,"totalDocs":1,"totalPages":1}