Creating A New Product: Are priorities really a priority?
Simon Pittman
Available for freelance web work! | WordPress support | Helping sole traders with their existing websites | Author of 7 books | Books & Networking
I'm currently working on new versions of my various products - some of them have quite a long list (including items that have been on the list for at least a few years!).
Upon reflection - some of these items may not be as important as when originally considered or added to the list - while some can wait until a future version (although if you keep putting it off until next release - is it really that important?).
Sometimes things change since I put together the list (for example, some items added before COVID whereas now one of the priorities is to implement items that make working from home easier for anyone using the software).
Items in the list already have priorities set (I use my own planning software - including using the software to plan the next version of my planning software!) - however are even the low priority tasks really a priority for the next versions of my products?
- Bug fixes will be at the top of your list of priorities.
- Take your time. Don't rush. It's better to do a few things really well, rather then rushing to get lots of things working.
- For any major new features/items - get the basic version working - it can be improved upon over subsequent versions and releases.
- Not just "code" - there is also documentation, support, etc. to consider and work on improving.
- Long list may not actually be a long list once you start working on the items. For example, many items may be bug fixes or minor improvements.
- Once an item is implemented in one product, it's easier to implement for other products. For example there will be code, components and knowledge that can be reused.
- Are items in the plans for my software really essential? Some items that may have seemed essential a few years ago may not be so anymore, and initial good ideas may not be so upon reflection.
- For tasks you may be putting off - get away from the screen, and sit down with a pen and paper and plan how that item will be implemented.
- Break the tasks down into smaller tasks will also help.
- Are there items that can wait until the next version? Although if you keep doing this, and pushing things back until the next release - when is it time to either implement the item, or stop pushing it back and remove from your plans?
- Remember it's sometimes good to improve existing aspects of a product, rather then working on the "next big thing" or constant new features. Some of my recent releases have done just this - improving existing parts of the software.
- How many people will use the improvement? Are you focusing on something only one or two people will use, rather then aspects that most people require or will actually make use of?
- Will the item on the list really help your clients? Really make their work easier?
Also avoid falling into the trap of spending too much time working on your software or product - that you forget marketing.
Whether it's a piece of paper or using planning software - having some form of plan will help. Just a short list, long list, or a full business plan - the important thing is to have a plan in place. While I've mentioned removing items from your plan - and plans will regularly be reviewed and revised - that doesn't mean that you should not stick to your plan!
Before starting work - that is a good point to review your list of tasks and look at what is really important, priorities, etc.
Sometimes upon reflection - especially with the next versions of my products I've been working on - I've been ruthless and decided the work is not essential - and removed the item from the list.
At the same time, don't just move tasks to the next version or remove them because they seem daunting - or you are trying to put that task off - in fact try and get those tasks done first (after any bug fixes) - sit down with a pen and paper, take your time and just focus on that task. Get the basic version working rather then being all singing, all dancing. Once you make a start it is likely to be much easier then you first believed.
Are there any tasks in your list of things to do that you have been putting off? Have a long list, and any tasks that may not be a priority and can wait (or be removed completely)?
Creating your own apps or software to sell?
There is a lot more involved then coding - there are many business aspects involved - including things to consider for commercial products, planning and release.
My book will help you create, release and sell your own products - available on Amazon at: https://www.amazon.co.uk/dp/B08C8R9R9W