Bullet points for requirements and one "box, swimlane, and cylinder" diagram (with no standard elements) for analysis and design if you're on a 'strict' project.

If we can't even decide on language A or B, CSV or JSON, ... (these are implementation artifacts that are essential to the solution), what hope do we have of even understanding- no even seeing that there is a problem in the other disciplines (requirements, analysis, etc) of technology delivery?

If we make it another 100 years, we'll look back at this time and view what we are coding now as wattle and daub huts whereas a century from now we'll be erecting the analogue of technological skyscrapers (but probably not good ones, if I'm being realistic).