This message was deleted.
# questions
b
This message was deleted.
c
Youtube series of start to finish process of developing a stacker solution. Starting from: • Gathering Business Requirements • Developing the different interfaces • Developing the permission model • Delivery
s
Thanks @clever-art-10420, love those - I think 1 and 4 are really interesting in particular, as they can be the hardest part - not just making something, but proper implementation / training etc.
c
I think one thing a lot of people struggle is what format to record the requirements in - both initially during discovery and than for handoff to the dev/tech person (if they are different people) Unfortunately Stacker is not intuitive enough that non-technical consultants can deliver it.
s
Really interesting, something we could perhaps all share experiences of.
c
Its definitely something I have been meaning to write about for a while. At some point I was planning to do a Freelancers 101 coarse, as after 8 years of consulting, starting as a freelancer, forming a coop and than forming an agency I think I have worked some things out (and have more to learn). I often coach people who are trying to transition from day job to freelancing/gig worker.
But thats more general stuff. Related to stacker specifically, I think a lot of people fail to push their clients to cut scope during discovery and than end up building things that were actually not needed, or at least not needed now now (as we say in New Zealand). One of the best exercises I have recently done is a visual roadmap in Figma. Basically we took the pages of the internal app we designed and than ordered them left to right as a prioritised development roadmap. After that we estimated each of the epics of work (pages). Then when the client told us the budget we could see how far down the roadmap that got them. It was really helpful to get the client to work out what they actually wanted.
💯 1
1
incidentally that was not a stacker app, but the UI was inspired by Stacker. I took the designer on a tour of a stacker app and showed them what I meant by “users can browse the data through clicking on related record links”. Once the designer understood this they put together a design for a react admin app for a white label product our client was building. (if your curios why we didn’t use stacker - not even to POC it was: 1. The user invitation flow with stacker is to slow/confusing. 2. We need to be able to duplicate the app and hook it up to a duplicated airtable base easily, reaching out to stacker support each time we want to duplicate was not an option)
👍 1
s
That's super helpful feedback about user invitation flow / app duplication. Certainly two things we want to look at. How would you feel about sharing some of your processes on a webinar (or some other format)? I'm particularly interested in how you visually roadmap solutions - could be super valuable not just for freelancers/agencies working with clients but also the no-code person in a business trying to convince colleagues.
c
I’d be happy too, I don’t have too much time atm. But in a few weeks I could do something.
🙌🏻 1
s
Nice! There's no rush, maybe later in the year. I'll DM you when I get thoughts together
1