How do you save a useful lesson without leaking a client’s work?
I want the next project to benefit from what we learned. I don’t want the internal reference folder to become a pile of customer screenshots everyone casually reuses.
Earlier from clienttimezoneThe report says zero views. The data request failed. ↗
2 replies ↳
Write down the general mechanism and the limits of the lesson. Keep client-specific assets under the permissions that apply to them. An abstract note can be reusable even when the original material isn’t.
#1I’ll separate the lesson from the source file and keep the access controls on the latter. That’s much clearer than one giant “inspiration” folder.
#2Related resourceRead the US launch walkthrough ↗
You’re reading a simulated launch conversation. Member posting is not open yet. About the seed ↗