large_Crossover Series NFTs.png

medium_Crossover Series NFTs.png

small_Crossover Series NFTs.png

thumbnail_Crossover Series NFTs.png

From Photography to NFT Art: Twisted Digital Landscapes with Nate Hill

From Design System to ‘NFT Design System’: Creating TinyFaces

Neurodiversity and Inclusion: Choosing Kinder Design

medium_652ccf22c8853584bde5553986a4eed0.png

small_652ccf22c8853584bde5553986a4eed0.png

thumbnail_652ccf22c8853584bde5553986a4eed0.png

Web5 is here. Goodbye Web3? TBD.

Published on <a href="https://blog.prototypr.io/startups-dont-get-lost-in-the-tech-45cd579aac5?source=rss----eb297ea1161a---4">| Prototyping: From UX to Front End &mdash; Medium</a> Nathan Allsopp 
<h4>There is more to success than good tech.</h4>
<img alt="" src="https://cdn-images-1.medium.com/max/1024/1*roedigbmFjRYkZobdZWuKg.jpeg">Ooh, pretty tech. Please may I have some tech? Image by <a href="https://unsplash.com/@markusspiske">Markus Spiske</a>
Take a look around your social networks and you’re bound to find someone you know venturing into “startup land”. Someone always has an awesome idea for a mobile app or online platform. The common problem that most of them have is&#8230;
<blockquote>I don’t know how to code!</blockquote>
Ah yes, this old gem — the punchline that everyone has heard before. This conundrum leads side-hustlers down the rabbit hole trying to find ways to build the codebase that underpins their idea.
Don’t get me wrong — finding a solution to this problem is necessary in order to start. However, this run down the rabbit hole seems to be a slippery slope for many startups.
The focus always seems to be “on the tech”. It’s what I like to call tech infatuation. Whether it is day 1 or day 100, many founders end up obsessed with the tech.
<blockquote>We can’t do that — because tech!. Need more tech. Forget the plan — tech. Wait, can you explain “the tech” again?</blockquote>
<blockquote>Tech. Tech. Tech. Goose.</blockquote>
All of a sudden, we’re in the situation of non-techs drowning in tech. Conversations about Elastic Beanstalk versus Heroku versus EC2 are going in one ear and out the other.
The tech is important, but it is only one part of the bigger picture. Focusing only on the technology means other key business functions may not be getting enough consideration.
These are the key areas that founders need to also focus on along the way.
<h4>User Research</h4>
<img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qIJemusUYX2d6oN5fNXCqQ.jpeg">Simply talking with people is a great way to learn more about your idea. <a href="https://unsplash.com/@rawpixel">Unsplash</a>
Having an idea is a great start, but in reality the idea is the smallest step of the journey.
You need to latch onto a problem that you can solve well and determine if the problem is large enough. Some ideas will be met with “Shut up and take my money!”, while others sound more like “That sounds like a nice thing to have”. Your product is the solution to your problem. Remember:
<blockquote>Problem first, product second. <a href="https://ctt.ec/gFZO8">Click to tweet.</a></blockquote>
Research is critical to ensure you’re solving a problem, and that there is a market for that problem. Put the tech and business plans down for a second, and really focus on the people. Listen to what they have to say. After all, they’re the ones who will pay you for the solution.
<h4>Product Design</h4>
<img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PfGrQ0o0O7i-gmsv1pWtGA.jpeg">Design is more than visuals — it is the way you solve your problem. <a href="https://unsplash.com/@rawpixel">Unsplash</a>
Many startups have a specific function in mind that forms the backbone of their idea. What many fail to consider is the overall solution that they’re trying to deliver.
Sure — every product needs pretty visuals and a few pages. But there’s more to it than just the aesthetics.
<blockquote>Problems need to be scoped, tested and validated.</blockquote>
<blockquote>Wireframes need to be created and validated.</blockquote>
<blockquote>Various design approaches need to be brainstormed and carefully considered.</blockquote>
<blockquote>Users (or potential users) need to be engaged with. Prototypes need to be created.</blockquote>
Crafting the entire visual solution to a problem is a task that is often underestimated. Your visuals are more than your visuals — they are how you solve the problem your company is based upon.
There is a huge world of Product Designers out there ready to help bring your idea visually to life, or you can choose from a range of basic design to get started. If budget is tight, tools such as <a href="https://www.sketchapp.com/">Sketchapp</a>, <a href="http://www.adobe.com/au/products/xd.html">Adobe XD</a> or <a href="https://www.figma.com/">Figma</a> are a great way to start alongside a few tutorials.
<h4>Documentation</h4>
<img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o9A5uTcfWZ2nc3epHe_LRg.jpeg">Documentation helps keep goals and objectives clear.
Ah, the funnest part of them all. Documentation may seem “fluffy” to some, but I’ve found it to be incredibly important.
When you’re building a product, communication is critical. When you’re not doing everything yourself, you need to be communicating clearly. If you do a poor job of explaining requirements to those building your product, unexpected surprises will pop-up along the way.
<blockquote>You thought you explained X, but you got Y. Small communication issues can equal big problems. <a href="https://ctt.ec/76dn1">Click to tweet.</a></blockquote>
As a result, documentation can be a great way to ensure everything is clear to the team involved. Put the tech aside and provide a breakdown of the idea and the concept. What actually needs to occur? What does a user need to be able to do and see? What does this function need to do?
<h4>Marketing</h4>
<img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RWDwC7a5f2yezgbXbfPI3A.jpeg">How people perceive and understand your product is critical. <a href="https://unsplash.com/photos/TaCk3NspYe0">Unsplash</a>
You may be building a great product, but you also need a great brand to act as the face of your product. The perceptions that people have about your brand play a key role in whether they’re likely to consider using your product or not.
As you go through the stages of building a product, you need to consider a few key Marketing activities that may help you gather some initial interest.
<ul>
<li>Do you have a brand name and logo?</li>
<li>What is your marketing plan around the product’s launch?</li>
<li>Do you have a website live to collect interest before you launch?</li>
<li>Have you considered what your key Marketing messages are?</li>
<li>Are presentation decks done and ready to go?</li>
<li>Do you have a content strategy to help build your brand reputation?</li>
<li>Have you considered what pricing strategy you will follow?</li>
</ul>
There are a lot of marketing activities to be done — even more could be added to the above list. Some may not be as significant as others, but collectively they all play important roles. My favourite thought is:
<blockquote>If users can see it, it needs to be thought about very carefully. <a href="https://ctt.ec/34cIQ">Click to tweet.</a></blockquote>
<h4>Business Development</h4>
<img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6WtigZRp_gyspZfRG0JGxg.jpeg">
Having a product is one thing, but getting people to use it and pay for it is another.
Reaching out to prospects, organising meetings, preparing presentations and closing deals takes times and effort. These activities are key for a startup as this is what brings in the revenue.
Talking with prospects also helps a startup learn what features are critical to their monetisation strategy. This helps teams better prioritise work to ensure roadmaps remain indicative of what are the most “in demand” features.
Taking the time to build relationships can give a startup plenty of opportunities they might not otherwise have. Sitting in and focusing on building your product won’t expose you to these relationships that could propel a product’s growth rapidly.
<h4>So, next time you’re focusing on the tech, be sure to ask yourself — am I too focused on the tech?</h4>
Nathan Allsopp is a <a href="https://www.nathanallsopp.com">Freelance Product/UI/UX Consultant</a> based in Sydney, Australia. This article appeared originally <a href="https://www.nathanallsopp.com/blog/startups-dont-get-lost-in-the-tech">here.</a>
<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff51076%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2Ff51076%2F&#038;image=https%3A%2F%2Fe.enpose.co%2F%3Fkey%3DdRXnS9Gplk%26w%3D700%26h%3D425%26url%3Dhttps%253A%252F%252Fupscri.be%252Ff51076%252F%253Fenpose&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0"><a href="https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href">https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&amp;referrerSource=full_rss&amp;postId=45cd579aac5" width="1" height="1" alt="stat?event=post.clientViewed&amp;referrerSou">
<hr>
<a href="https://blog.prototypr.io/startups-dont-get-lost-in-the-tech-45cd579aac5">Startups — don’t get lost in the tech</a> was originally published in <a href="https://blog.prototypr.io">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.

Startups — don’t get lost in the tech

Startups — don’t get lost in the tech

There is more to success than good tech.

Top Stories